Skip to content
Noroxi
CVE-2023-29294· NVD / CVE Program· CNA adobe

Bypass Purchase Order Approval using Company User in Adobe Commerce B2B

Adobe Commerce versions 2.4.6 (and earlier), 2.4.5-p2 (and earlier) and 2.4.4-p3 (and earlier) are affected by a Business Logic Errors vulnerability that could result in a security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass a minor functionality. Exploitation of this issue does not require user interaction.

MediumCVSS 4.3 · v3.1—No exploit Fix available
Published
Jun 15, 2023
Updated
Jun 17, 2026
EPSS
0.7% · 53th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

17

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · adobe
4.3
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
adobecommerce
adobemagento

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • adobe commerce2.3.7
  • adobe commerce2.4.0
  • adobe commerce2.4.1
  • adobe commerce2.4.2
  • adobe commerce2.4.3
  • adobe commerce2.4.4
  • adobe commerce2.4.5
  • adobe commerce2.4.6
  • adobe magento2.4.4
  • adobe magento2.4.5
  • adobe magento2.4.6

Versions reported by the vendor

Affected version ranges reported by the assigning authority (adobe). Independent of NVD's CPE analysis and usually ahead of it.

  • Adobe Magento Commerce

    • unspecified and later · up to and including 2.4.6affected
    • unspecified and later · up to and including 2.4.5-p2affected
    • unspecified and later · up to and including 2.4.4-p3affected
    • unspecified and later · up to and including Noneaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Packagistmagento/community-editionfrom 2.4.4-p1 · before 2.4.4-p42.4.4-p4
Packagistmagento/community-editionfrom 2.4.5-p1 · before 2.4.5-p32.4.5-p3
Packagistmagento/community-editionall versions—
Packagistmagento/project-community-editionup to and including 2.0.2—

Same product

adobe: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-34102XXE can expose crypt key and other secrets granting full admin accessKEV
    99Now
  • CVE-2022-24086Adobe Commerce checkout improper input validation leads to remote code executionKEV
    99Now
  • CVE-2025-54236Adobe Commerce | Improper Input Validation (CWE-20)KEV
    94Now
  • CVE-2026-71362Adobe Commerce | Incorrect Authorization (CWE-863)KEV
    92Now
  • CVE-2026-75650Adobe Commerce | Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336)KEV
    71This week
  • CVE-2025-24434Adobe Commerce | Incorrect Authorization (CWE-863)
    41Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Packagist:magento/community-edition2.4.4-p4Package registry (OSV)
Packagist:magento/community-edition2.4.5-p3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-840 · Business Logic Errors

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records