dbcve.org
CommerceApplication · Adobe

CVE-2025-24437

MEDIUM · 5.4 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 →
60/100
Remediation priority · Elevated
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.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11, 2.4.8-beta1 and earlier are affected by an Incorrect Authorization vulnerability that could result in a security feature bypass. A low-privileged attacker could exploit this vulnerability to view or modify select information. 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 low-privileged attackers to bypass security features and view or modify select information without user interaction. The vulnerability affects versions 2.4.4-p11 through 2.4.7-p3 and earlier versions, including the beta.

MitigationApply the vendor security patch or update to Adobe Commerce version 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, or 2.4.4-p11 or later to remediate the authorization bypass.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 checks

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

  1. Check Adobe Commerce version via command line
    Run 'bin/magento --version' in the Magento root directory to obtain the installed version string
    Affected if The version output is 2.4.4, 2.4.5, 2.4.6, 2.4.7, or 2.4.8 (any patch level) or falls within 2.4.4-p11 through 2.4.7-p3 range, indicating an affected version
  2. Check Adobe Commerce version via composer.json
    Open the composer.json file in the Magento root directory and examine the 'version' field or the installed packages via 'composer show magento/framework'
    Affected if The reported version matches 2.4.4 through 2.4.7-p3 or earlier versions like 2.4.4-p10 and below, indicating an affected version
  3. Check Adobe Commerce B2B version
    Run 'composer show magento/module-b2b' or examine the composer.json for the B2B module version
    Affected if The B2B module version is 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.0, indicating an affected B2B installation
  4. Check Adobe Magento version via admin panel
    Log into the Adobe Commerce/Magento admin panel and scroll to the footer area to view the version number displayed there
    Affected if The admin panel footer shows a version within 2.4.4 through 2.4.7-p3 or earlier, indicating the environment is affected

The environment is affected if the installed Adobe Commerce, Adobe Commerce B2b, or Adobe Magento version falls within 2.4.4-p11 through 2.4.7-p3 or matches any of the specific versions listed (2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8 for Commerce/Magento, or 1.3.3 through 1.5.0 for B2B).

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 security patch or update to Adobe Commerce version 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, or 2.4.4-p11 or later to remediate the authorization bypass.

Recommended fix High confidence

Upgrade to one of the fixed patch versions: 2.4.4-p11, 2.4.5-p10, 2.4.6-p8, or 2.4.7-p3 (or later stable release)

  1. Check your current Adobe Commerce or Magento installation version using the command line or admin panel
  2. Access the Adobe Security Patch Bulletin at helpx.adobe.com to obtain the specific patch for your version (e.g., MDVA-XXXXX for CVE-2025-24437)
  3. Backup your entire Adobe Commerce/Magento database and files before applying any patches
  4. Apply the appropriate security patch using the command line: patch -p1 < patch_file.patch
  5. Verify the patch was applied successfully by checking for any errors during installation
  6. Clear the Magento cache by running bin/magento cache:flush
  7. Verify the fix by confirming the patch version matches the fixed release (2.4.4-p11, 2.4.5-p10, 2.4.6-p8, or 2.4.7-p3)
Caveat Patches are generally safe but test in staging first; upgrading to a new minor version may introduce breaking changes to custom code or extensions

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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