dbcve.org
CommerceApplication · Adobe

CVE-2026-47988

HIGH · 8.6 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 1.21.0 or later.
See remediation →
95/100
Remediation priority · Urgent
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 and limited write access, causing a limited disruption to availability. 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. Attackers can gain unauthorized read and limited write access without any user interaction, exploiting the authorization mechanism to circumvent security controls.

MitigationApply the vendor-provided security patch for Adobe Commerce immediately. Review and audit existing authorization controls and user access permissions as a defensive measure.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

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

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 'php bin/magento --version' from the web root directory, or check the version in the admin panel under System > Configuration > Advanced > Developer > Version. For Adobe I/O Events, check the installed package version via 'composer show adobe-commerce/adobe-io-events' or check composer.json.
    Affected if The installed version matches exactly 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9 for Adobe Commerce/Magento; or matches 1.3.3, 1.3.4, 1.4.2, 1.5.2, or 1.5.3 for Adobe Commerce B2b; or Adobe I/O Events version is >= 1.6.0 and < 1.21.0.
  2. Confirm Adobe Commerce B2B module is installed
    Check for the presence of the B2B module by examining the composer.json file for 'magento/module-b2b' or run 'php bin/magento module:status' and look for Magento_B2b in the output list.
    Affected if The B2B module is installed and its version matches 1.3.3, 1.3.4, 1.4.2, 1.5.2, or 1.5.3.
  3. Verify if REST or GraphQL API endpoints are publicly accessible
    Test access to common API endpoints without authentication: try GET requests to /rest/V1/products/1 or /graphql endpoint without providing authorization headers. Check the etc/webapi.xml configuration files to review which routes are defined with anonymous access.
    Affected if API endpoints that should require authentication are accessible without valid authorization tokens.
  4. Inspect admin configuration for authorization settings
    Navigate to Stores > Settings > Configuration > Security in the admin panel and verify the 'Admin Account Sharing' and 'Maximum Login Failures to Lock' settings. Check if any custom API role permissions grant broader access than intended under System > Permissions > API Roles.
    Affected if Authorization settings are misconfigured allowing unauthenticated or under-privileged access to sensitive operations.
  5. Review Adobe I/O Events configuration if applicable
    If Adobe I/O Events is installed, examine the configuration file app/etc/config.php for 'adobe_io_events' entry and check the events configuration in the admin panel under Stores > Configuration > Adobe I/O Events to see which event listeners are enabled.
    Affected if Adobe I/O Events is enabled and the version falls within the affected range.

You are affected if your installed Adobe Commerce, Magento, Commerce B2b, or Adobe I/O Events version exactly matches one of the versions listed in the affected versions, and unauthenticated API access is possible.

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 immediately. Review and audit existing authorization controls and user access permissions as a defensive measure.

Recommended fix Moderate confidence

Adobe Commerce security patch or version >= 2.4.7-pX (specific patch version per Adobe bulletin)

  1. Check Adobe Commerce security release notes on helpx.adobe.com for the specific patch or version containing the fix for CVE-2026-47988
  2. Identify the current Adobe Commerce version using bin/magento --version or the admin panel footer
  3. Review the Adobe security bulletin for the recommended fixed version or available patches
  4. Plan and schedule the upgrade or patch installation in a non-production environment first
  5. Test the upgrade/patch thoroughly in a staging environment before deploying to production
  6. Apply the upgrade following Adobe's official upgrade documentation for your specific version
  7. Verify the vulnerability is resolved by confirming the version includes the security fix
Caveat Review Adobe's release notes for any breaking changes or backward compatibility issues in the security patch release

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

Fix this in Commerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47988 — 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-47988 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