dbcve.org
CommerceApplication · Adobe

CVE-2025-24411

HIGH · 8.1 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 1.3.3 / 2.4.4 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 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 Access Control vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized access affecting Confidentiality and Integrity. 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 confidence

This is an Improper Access Control vulnerability in Adobe Commerce (Magento) affecting versions 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier. A low-privileged attacker can bypass security measures to gain unauthorized access, impacting confidentiality and integrity. No user interaction is required for exploitation.

MitigationApply the vendor-provided security patch or upgrade to a patched Adobe Commerce version (2.4.4-p11 or higher for the 2.4.4 branch, 2.4.5-p10 or higher for the 2.4.5 branch, etc.). Test thoroughly in a staging environment before production deployment.

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.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8
Commerce B2bApplication
Affected:< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.0
MagentoCMS
Affected:< 2.4.4= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8

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
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 checks

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

  1. Check Adobe Commerce version
    Run the command 'php bin/magento --version' or check the composer.json file in the Magento root directory for the version entry
    Affected if The installed version is 2.4.8-beta1, 2.4.7-p3 or lower, 2.4.6-p8 or lower, 2.4.5-p10 or lower, 2.4.4-p11 or lower, or any version below 2.4.4
  2. Check Adobe Commerce B2B extension version
    Run 'composer show magento/module-b2b' or check the composer.lock file for the magento/module-b2b package version
    Affected if The B2B extension version is 1.3.3, 1.3.4, 1.3.5, 1.4.2, 1.5.0, or any version below 1.3.3
  3. Check Adobe Magento version
    Run 'php bin/magento --version' if using Magento Open Source, or check the version in the admin panel under System > Settings > Configuration > Advanced > Developer
    Affected if The installed Magento version matches the same vulnerable version ranges as Adobe Commerce (2.4.4 through 2.4.8 inclusive and earlier)
  4. Verify if the application is exposed to the network
    Confirm whether the Magento instance is accessible from the network or internet, as exploitation requires no user interaction
    Affected if The vulnerable Adobe Commerce or Magento instance is network-accessible without proper firewall or access control restrictions

The environment is affected if Adobe Commerce, Adobe Commerce B2b, or Magento Open Source is installed and the version falls within 2.4.4 through 2.4.8 (inclusive) or earlier than 2.4.4, or if B2b extension version is 1.3.3 through 1.5.0 inclusive or below 1.3.3.

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.3.3 / 2.4.4 or later
Fixed in 1.3.32.4.4
Interim mitigation

Apply the vendor-provided security patch or upgrade to a patched Adobe Commerce version (2.4.4-p11 or higher for the 2.4.4 branch, 2.4.5-p10 or higher for the 2.4.5 branch, etc.). Test thoroughly in a staging environment before production deployment.

Recommended fix High confidence

Adobe Commerce 2.4.7-p4+ (recommended stable) or 2.4.6-p9+; Commerce B2B 1.3.3-p4+, 1.3.4-p4+, or 1.3.5-p3+

  1. 1. Identify your current Adobe Commerce/Magento version by checking the composer.json or admin panel.
  2. 2. For Commerce 2.4.4: Upgrade to 2.4.4-p12 or later (or migrate to 2.4.7-p4 or later, or 2.4.6-p9 or later).
  3. 3. For Commerce 2.4.5: Upgrade to 2.4.5-p11 or later (or migrate to 2.4.7-p4 or later, or 2.4.6-p9 or later).
  4. 4. For Commerce 2.4.6: Upgrade to 2.4.6-p9 or later (or migrate to 2.4.7-p4 or later).
  5. 5. For Commerce 2.4.7: Upgrade to 2.4.7-p4 or later.
  6. 6. For Commerce B2B 1.3.3: Upgrade to 1.3.3-p4 or later.
  7. 7. For Commerce B2B 1.3.4: Upgrade to 1.3.4-p4 or later.
  8. 8. For Commerce B2B 1.3.5: Upgrade to 1.3.5-p3 or later.
Caveat Review Adobe Commerce upgrade documentation for potential compatibility issues; test thoroughly in staging before production deployment

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
  • Testing10.0 h
  • Review / QA3.0 h
22.0 hours of engineering $3,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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