dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 14 Nov 2025.
CommerceApplication · Adobe

CVE-2025-54236

CRITICAL · 9.1 CVSS v3.1 Published 2025-09-09
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
In the wild High EPSS Public exploit 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.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, 2.4.4-p15 and earlier are affected by an Improper Input Validation vulnerability. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality, and integrity impact to high. 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 improper input validation vulnerability (CVSS 9.1) that allows unauthenticated attackers to achieve session takeover by manipulating input parameters, granting high confidentiality and integrity impact without requiring user interaction.

MitigationApply the vendor-supplied security patches for the affected Adobe Commerce versions (2.4.4-p15, 2.4.5-p14, 2.4.6-p12, 2.4.7-p7, 2.4.8-p2, 2.4.9-alpha2 and earlier) to remediate the improper input validation vulnerability.

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= 2.4.9
Commerce B2bApplication
Affected:= 1.3.3= 1.3.4= 1.4.2= 1.5.2= 1.5.3
MagentoCMS
Affected:= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9

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 the installed Adobe Commerce version via CLI
    Run `bin/magento --version` or `composer show magento/product-community-edition` to retrieve the exact version number
    Affected if The version shown is 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9 (any patch level)
  2. Check the Adobe Commerce B2B module version
    Run `composer show magento/module-b2b` if the B2B module is installed, or inspect the composer.lock file for the b2b module version
    Affected if The B2B module version is 1.3.3, 1.3.4, 1.4.2, 1.5.2, or 1.5.3
  3. Verify the Magento Open Source version if applicable
    If using Magento Open Source rather than Adobe Commerce, run `bin/magento --version` or check composer.json for the magento/magento2-base package version
    Affected if The version is 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9
  4. Confirm whether security patches have been applied
    Check the app/etc/config.php file or look for applied patch files in the patches directory, or run `git status` to see if local patch files exist
    Affected if No Adobe security patches for this CVE (2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, or 2.4.4-p15) have been applied to the installation

You are affected if your Adobe Commerce, Adobe Commerce B2b, or Magento Open Source installation runs any of the listed versions without the corresponding security patch applied.

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-supplied security patches for the affected Adobe Commerce versions (2.4.4-p15, 2.4.5-p14, 2.4.6-p12, 2.4.7-p7, 2.4.8-p2, 2.4.9-alpha2 and earlier) to remediate the improper input validation vulnerability.

Recommended fix High confidence

Adobe Commerce 2.4.9 (latest stable 2.4.x release)

  1. 1. Backup your Adobe Commerce/Magento database and filesystem before proceeding
  2. 2. Review the release notes for the latest Adobe Commerce 2.4.x release to understand changes
  3. 3. Update your composer.json to require the latest 2.4.x version (e.g., magento/product-community-edition 2.4.9 or later)
  4. 4. Run composer update to fetch the new packages
  5. 5. Run bin/magento setup:upgrade to apply database migrations
  6. 6. Clear caches with bin/magento cache:flush
  7. 7. Re-index with bin/magento indexer:reindex
  8. 8. Verify the application loads correctly and test critical user flows
Caveat Review release notes for any breaking changes between your current version and 2.4.9; test in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Commerce Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
40.0 hours of engineering $6,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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