CVE-2025-24418
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 versions 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier are affected by an Improper Authorization vulnerability that could result in Privilege escalation. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized 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 · high confidenceAdobe Commerce contains an improper authorization vulnerability that allows a low-privileged attacker to bypass security measures and escalate privileges to gain unauthorized administrative access. The vulnerability requires no user interaction to exploit.
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< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Adobe Commerce B2b versionRun the command 'php bin/magento --version' or check the composer.json file for the 'magento/product-b2b' package versionAffected if The installed version is < 1.3.3, = 1.3.3, = 1.3.4, = 1.3.5, = 1.4.2, or = 1.5.0
-
Verify B2b module is enabledRun 'php bin/magento module:status Magento_B2b' or check app/etc/config.php for 'Magento_B2b' being set to 1Affected if The B2b module is enabled (this is required for the vulnerability to be exploitable)
-
Review admin user accounts for unauthorized creationQuery the admin_user table in the database: SELECT * FROM admin_user; or check for unexpected admin accounts via the admin panel under System > All UsersAffected if There are admin user accounts that were not created by legitimate administrators, especially accounts with escalated privileges
-
Check admin action logs for privilege escalationReview the admin_actions_history table or admin_log table for suspicious activity around user privilege changes, particularly actions performed by low-privileged usersAffected if There are records of privilege escalation or admin access from users who should not have administrative rights
-
Inspect admin permissions configurationCheck the authorization role tables (admin_rule) for unexpected changes to role permissions, or review the acl.xml files in custom modules for modifications allowing privilege escalationAffected if Roles or permissions have been modified to grant elevated access to low-privileged users
Your environment is affected if Adobe Commerce B2b is installed with a version matching the affected ranges listed above and the B2b module is enabled.
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.3.3
Upgrade Adobe Commerce to the patched versions (2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 or later) as specified in the Adobe security bulletin, after testing in a staging environment.
Commerce B2b extension version 1.3.6 or later
- 1. Verify current Commerce B2b extension version in composer.json or the admin panel under 'Component Manager'
- 2. Create a full backup of the Magento database and codebase
- 3. Update the Commerce B2b extension via composer: composer require magento/module-b2b:1.3.6 --no-update
- 4. Run composer update magento/module-b2b to install the fixed version
- 5. Clear the Magento cache: php bin/magento cache:clean
- 6. Reindex if necessary: php bin/magento indexer:reindex
- 7. Verify the new version is installed: composer show magento/module-b2b
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24418 — 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-2025-24418 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