dbcve.org
CommerceApplication · Adobe

CVE-2025-24438

HIGH · 8.7 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 →
91/100
Remediation priority · Urgent
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.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low-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 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

Stored XSS vulnerability in Adobe Commerce allows low-privileged attackers to inject malicious JavaScript into form fields. When victims view the affected page, the stored script executes in their browser, enabling session hijacking and potential data theft.

MitigationApply vendor-released security patches for affected versions and implement output encoding/ input validation on all user-controllable form fields.

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 or Magento version
    Run the command: php bin/magento --version or check the composer.json file in the web root for the version number
    Affected if The version matches 2.4.4, 2.4.5, 2.4.6, 2.4.7, or 2.4.8 for Adobe Commerce/Magento, or 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.0 for Adobe Commerce B2b
  2. Confirm customer account registration is enabled
    Log into the admin panel, navigate to Stores > Configuration > Customers > Customer Configuration > Account Options, and verify that Allow Customer Registration is set to Yes
    Affected if Customer registration is enabled and the version is in the affected list
  3. Review form fields accessible to low-privileged users
    Inspect forms accessible to unauthenticated or customer-level users, such as registration forms, review forms, contact forms, or address book forms. Check the HTML source for input fields and their name attributes
    Affected if Forms accepting user input are present and accessible without admin privileges
  4. Check for stored XSS payloads in database
    Query the database for potential XSS payloads in customer-submitted fields. Example: SELECT * FROM customer_entity WHERE email LIKE '%<script%' OR firstname LIKE '%<script%' OR lastname LIKE '%<script%'
    Affected if Records containing script tags or HTML in user-editable fields are found in the database

You are affected if your installed Adobe Commerce or Magento version matches one of the listed affected versions AND low-privileged users can submit data to form fields that are not properly sanitized or encoded on output.

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-released security patches for affected versions and implement output encoding/ input validation on all user-controllable form fields.

Recommended fix High confidence

Upgrade to Adobe Commerce 2.4.8 or later, or apply security patches: 2.4.4-p12, 2.4.5-p11, 2.4.6-p9, or 2.4.7-p4 (whichever applies to your current version)

  1. 1. Identify the current Adobe Commerce/Magento version by running: bin/magento --version or checking the composer.json file
  2. 2. Determine the appropriate upgrade path based on your current version (see upgrade_path)
  3. 3. Create a complete backup of the codebase, database, and media files before proceeding
  4. 4. Test the upgrade in a staging environment that mirrors production
  5. 5. For patch-based fixes, apply the latest security patch corresponding to your version (e.g., patch for 2.4.4-p12, 2.4.5-p11, 2.4.6-p9, or 2.4.7-p4)
  6. 6. Run bin/magento setup:upgrade after applying patches
  7. 7. Clear caches: bin/magento cache:flush
  8. 8. Reindex if necessary: bin/magento indexer:reindex
Caveat Review Adobe Commerce 2.4.8 release notes for any breaking changes; major version upgrades may require PHP version updates and compatibility checks with third-party 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-24438 — 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-24438 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