dbcve.org
CommerceApplication · Adobe

CVE-2026-47997

MEDIUM · 5.9 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 1.21.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Adobe Commerce is affected by an Incorrect Authorization vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized read access. Exploit depends on conditions beyond the attacker's control. Exploitation of this issue does not require user interaction.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Adobe Commerce contains an Incorrect Authorization vulnerability allowing security feature bypass. An attacker could exploit this to gain unauthorized read access to sensitive data without user interaction, though exploitation depends on conditions beyond the attacker's control.

MitigationApply the vendor-provided security patch for Adobe Commerce and review authorization controls to ensure proper access restrictions are enforced.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CommerceApplication
Affected:= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9
Commerce B2bApplication
Affected:= 1.3.3= 1.3.4= 1.4.2= 1.5.2= 1.5.3
MagentoCMS
Affected:= 2.4.6= 2.4.7= 2.4.8= 2.4.9
I\/o EventsApplication
Affected:>= 1.6.0, < 1.21.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Adobe Commerce or Magento version
    Run `composer show magento/product-community-edition 2>/dev/null | grep version` or `bin/magento --version` from the Magento root directory. Alternatively, check composer.json for the version entry.
    Affected if The version matches 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9.
  2. Identify Adobe Commerce B2B version if installed
    Run `composer show magento/module-b2b 2>/dev/null | grep version` or check composer.json for the b2b module version.
    Affected if The B2B module version matches 1.3.3, 1.3.4, 1.4.2, 1.5.2, or 1.5.3.
  3. Identify Adobe I/O Events version
    Check composer.json or run `composer show adobe/io-events 2>/dev/null | grep version` if the Adobe I/O Events module is installed.
    Affected if The I/O Events version is >= 1.6.0 and < 1.21.0.
  4. Verify if the instance exposes API endpoints or integration modules
    Review etc/webapi.xml configuration files and check for exposed REST/SOAP API endpoints. Look for any custom or third-party modules that register web API routes in the `etc/webapi.xml` file.
    Affected if API endpoints are exposed and the product version is in the affected range listed above, creating a potential attack surface for unauthorized data access.

The environment is likely affected if any installed component (Adobe Commerce, Magento, B2B, or I/O Events) matches the specific version numbers listed in the affected versions, as the incorrect authorization flaw could allow unauthorized read access to sensitive data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.21.0 or later
Fixed in 1.21.0
Interim mitigation

Apply the vendor-provided security patch for Adobe Commerce and review authorization controls to ensure proper access restrictions are enforced.

Recommended fix Moderate confidence

Adobe Commerce/Magento 2.4.7-p5+ or latest stable 2.4.x release; I/O Events 1.21.0+

  1. 1. Identify your current Adobe Commerce or Magento version by checking the admin panel or composer.json
  2. 2. For Adobe Commerce 2.4.4-2.4.7: Apply security patch ACPU-2025-47997 (or latest available security patch for your version)
  3. 3. For Magento Open Source 2.4.6-2.4.9: Apply corresponding security patch (e.g., MDVA-XXXXX) or upgrade to the latest stable version
  4. 4. For Commerce B2B extension: Update to version 1.5.3 or later which contains the fix
  5. 5. For I/O Events extension: Update to version 1.21.0 or later
  6. 6. Clear Magento cache after applying patches: bin/magento cache:clean
  7. 7. Verify the fix by testing authorization controls for affected modules
Caveat Review Adobe Commerce release notes for security patch compatibility; some patches may require specific Magento version prerequisites

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Commerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47997 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47997 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data