CVE-2026-47984
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 · uneditedAdobe 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. 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 confidenceThis is an Incorrect Authorization vulnerability in Adobe Commerce that allows attackers to bypass security measures and gain unauthorized read and write access to the application. The vulnerability can be exploited without any user interaction, making it particularly dangerous. The core issue involves improper validation of authorization checks that should control access to sensitive functions or data.
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= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9= 1.3.3= 1.3.4= 1.4.2= 1.5.2= 1.5.3= 2.4.6= 2.4.7= 2.4.8= 2.4.9>= 1.6.0, < 1.21.0CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Adobe Commerce or Magento versionRun the command bin/magento --version from the web root directory, or check the composer.json file for the magento/product-community-edition or magento/product-enterprise-edition version numberAffected if The version matches exactly 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9
-
Verify if Adobe Commerce B2B extension is installedCheck composer.json for magento/module-b2b or run bin/magento module:status | grep B2bAffected if The B2B extension version matches exactly 1.3.3, 1.3.4, 1.4.2, 1.5.2, or 1.5.3
-
Check if Adobe I/O Events module is enabledRun bin/magento module:status | grep AdobeIoEvents or inspect the app/etc/config.php file for Adobe_IoEvents module entryAffected if The module is enabled and its version is >= 1.6.0 and < 1.21.0
-
Review admin access logs for unauthorized access patternsExamine var/log/admin.log or the database table admin_user_session for login attempts from unexpected IP addresses or repeated failed authorization attemptsAffected if There are successful admin logins or API authorization events that originate from unexpected sources or show authorization bypass patterns
-
Check if the admin panel or REST API is internet-facingReview network configuration or web server settings to determine if /admin, /rest/, or /graphql endpoints are accessible from public IP addresses without IP restrictionAffected if Administrative or API endpoints are exposed to the public internet without IP allow-listing or additional authentication layers
Your environment is affected if you are running any of the listed Adobe Commerce, Magento, or B2B versions (or Adobe I/O Events 1.6.0 to <1.21.0) and your admin/API interfaces are accessible without network-level access controls.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.21.0
Apply the official Adobe Commerce security patch for CVE-2026-47984 immediately, as this is a critical authorization bypass. In the interim, restrict administrative and API access to trusted IP addresses via network-level controls and implement additional monitoring for suspicious access patterns.
Adobe Commerce 2.4.7-p1+ / Magento Open Source 2.4.9-p1+ / I/O Events 1.21.0+
- Check your current Adobe Commerce/Magento version by running: bin/magento --version or viewing version.php in the app directory
- For Adobe Commerce (2.4.4-2.4.7): Upgrade to Adobe Commerce 2.4.7-p1 or later which contains the security patch for this vulnerability
- For Magento Open Source (2.4.6-2.4.9): Upgrade to Magento Open Source 2.4.9-p1 or later
- For Commerce B2B (1.3.3-1.5.2): Upgrade to Commerce B2B 1.5.3 or later which includes the security fix
- For I/O Events (1.6.0 to <1.21.0): Upgrade to I/O Events version 1.21.0 or later
- After upgrade, clear Magento cache: bin/magento cache:clean && bin/magento cache:flush
- Verify the fix by checking Adobe Security Bulletin (helpx.adobe.com) for CVE-2026-47984 confirmation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47984 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47984 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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