dbcve.org
CommerceApplication · Adobe

CVE-2025-24434

CRITICAL · 9.1 CVSS v3.1 Published 2025-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Incorrect Authorization vulnerability that could result in Privilege escalation. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized access. Exploitation of this issue does not require user interaction. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality and integrity impact as high.

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

Adobe Commerce contains an Incorrect Authorization vulnerability allowing privilege escalation that enables attackers to bypass security measures and achieve session takeover without user interaction. The flaw affects multiple versions from 2.4.4-p11 through 2.4.8-beta1, with a CVSS 9.1 critical rating indicating severe impact on confidentiality and integrity.

MitigationApply the vendor-provided security patches for Adobe Commerce versions 2.4.4-p11, 2.4.5-p10, 2.4.6-p8, 2.4.7-p3, and 2.4.8-beta1. Prioritize patching given the critical severity and no-user-interaction exploitation vector.

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
Commerce B2bApplication
Affected:= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.0
MagentoCMS
Affected:= 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed Adobe Commerce version
    Run command: bin/magento --version or check composer.json for version entry
    Affected if Version matches 2.4.4, 2.4.5, 2.4.6, 2.4.7, or 2.4.8 (including patch versions like -p11 through -p8, beta1)
  2. Verify Adobe Commerce B2B extension version
    Run command: bin/magento module:status Magento_B2b or check composer.json for magento/module-b2b version
    Affected if B2B extension version is 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.0
  3. Confirm Magento Open Source version
    Check app/etc/env.php for edition type, or run: bin/magento admin:user:list to identify if community edition is in use
    Affected if Magento version matches 2.4.4, 2.4.5, 2.4.6, 2.4.7, or 2.4.8 and is the affected release line
  4. Check admin user account configuration
    Query admin_user table or run: bin/magento admin:user:list to enumerate existing admin accounts
    Affected if Multiple admin accounts exist with varying privilege levels, indicating privilege escalation is possible

Your environment is affected if Adobe Commerce, Magento Open Source, or B2B extension version falls within 2.4.4 through 2.4.8 or the specified B2B versions, since the incorrect authorization vulnerability allows privilege escalation without user interaction.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided security patches for Adobe Commerce versions 2.4.4-p11, 2.4.5-p10, 2.4.6-p8, 2.4.7-p3, and 2.4.8-beta1. Prioritize patching given the critical severity and no-user-interaction exploitation vector.

Recommended fix High confidence

Upgrade to the latest stable release (recommended 2.4.8 or the latest 2.4.7-patch for your current line)

  1. Check your current Adobe Commerce or Magento version by running: bin/magento --version or checking composer.json
  2. Backup your database and codebase before upgrading
  3. For Adobe Commerce 2.4.4: Upgrade to 2.4.4-p11 or later
  4. For Adobe Commerce 2.4.5: Upgrade to 2.4.5-p10 or later
  5. For Adobe Commerce 2.4.6: Upgrade to 2.4.6-p8 or later
  6. For Adobe Commerce 2.4.7: Upgrade to 2.4.7-p3 or later
  7. If on Adobe Commerce 2.4.8-beta1, upgrade to the stable 2.4.8 release
  8. For Adobe Commerce B2B: Ensure the corresponding base Commerce version is patched as above, then update B2B extension to compatible version
Caveat Check Adobe Commerce upgrade documentation for breaking changes between minor versions; 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
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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