dbcve.org
CommerceApplication · Adobe

CVE-2025-54264

HIGH · 8.1 CVSS v3.1 Published 2025-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
85/100
Remediation priority · High
Remotely reachable

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 a stored Cross-Site Scripting (XSS) Cross-Site Scripting (XSS) vulnerability that could be abused by a high-privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality, and integrity impact to high. Exploitation of this issue requires user interaction in that a victim must browse to the page containing the vulnerable field. Scope is changed.

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Commerce allows high-privileged attackers to inject malicious JavaScript into vulnerable form fields. When victims browse to pages containing the injected scripts, the malicious code executes in their browsers, potentially enabling session takeover.

MitigationApply vendor-supplied 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, and 2.4.9-alpha2). Implement output encoding and input validation on the affected form fields to prevent script injection.

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.3.5= 1.4.2= 1.5.2= 1.5.3
MagentoCMS
Affected:= 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
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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 'composer show magento/product-community-edition 2>/dev/null | grep version' or access the admin panel and check System > Configuration > General > Advanced > Advanced and look for the version string, or check the composer.json file in the installation root for the magento/magento2-base package version
    Affected if The installed version matches 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9 exactly
  2. Identify installed Adobe Commerce B2B version
    Run 'composer show magento/module-b2b 2>/dev/null | grep version' or check the composer.json for the b2b module version
    Affected if The installed B2B module version matches 1.3.3, 1.3.4, 1.3.5, 1.4.2, 1.5.2, or 1.5.3 exactly and the base Commerce version is also affected
  3. Identify installed Magento Open Source version
    Check the composer.json file for magento/magento2-base version or run bin/magento --version if the CLI is available
    Affected if The installed Magento Open Source version matches 2.4.6, 2.4.7, 2.4.8, or 2.4.9 exactly
  4. Audit admin-accessible form fields for injected script content
    Query the database for unencoded script tags in tables that store form input (such as catalog product attributes, category descriptions, CMS blocks, or customer address fields). Example SQL: SELECT * FROM catalog_product_entity_text WHERE value LIKE '%<script%' OR value LIKE '%javascript:%'
    Affected if Any form field records contain raw script tags or javascript: URIs that were not properly sanitized on output, indicating active exploitation of this stored XSS vulnerability

You are affected if your installed Adobe Commerce, Commerce B2B, or Magento Open Source version matches any of the specific versions listed AND suspicious unencoded script content exists in form field data stored in your database.

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 vendor-supplied 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, and 2.4.9-alpha2). Implement output encoding and input validation on the affected form fields to prevent script injection.

Recommended fix High confidence

Apply the corresponding security patch (2.4.4-p15, 2.4.5-p14, 2.4.6-p12, 2.4.7-p7, 2.4.8-p2, or 2.4.9-alpha2) for your current version

  1. 1. Identify the current Adobe Commerce or Magento version by running: bin/magento --version or checking the version in the admin panel under System > Configuration > Advanced > Admin > Admin Base URL
  2. 2. Based on the current version, download the corresponding security patch from the Adobe Security Patch Catalog (helpx.adobe.com/security/products/magento/apsb25-11.html)
  3. 3. For version 2.4.4: Apply patch CE-2.4.4-p15.patch
  4. 4. For version 2.4.5: Apply patch CE-2.4.5-p14.patch
  5. 5. For version 2.4.6: Apply patch CE-2.4.6-p12.patch
  6. 6. For version 2.4.7: Apply patch CE-2.4.7-p7.patch
  7. 7. For version 2.4.8: Apply patch CE-2.4.8-p2.patch
  8. 8. For version 2.4.9: Apply patch CE-2.4.9-alpha2.patch

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

Fix this in Commerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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