dbcve.org
CommerceApplication · Adobe

CVE-2025-24415

HIGH · 8.7 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 1.3.3 / 2.4.4 or later.
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 Cross-Site Scripting (XSS) vulnerability in Adobe Commerce allows low-privileged attackers to inject malicious JavaScript into form fields. When victims browse pages containing the injected scripts, the payloads execute in their browsers, enabling session takeover and high confidentiality/integrity impact.

MitigationApply Adobe security patches for the affected versions (2.4.4-p11, 2.4.5-p10, 2.4.6-p8, 2.4.7-p3, 2.4.8-beta1) or upgrade to a patched version, ensuring all user-supplied form input is properly sanitized and output-encoded.

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.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8
Commerce B2bApplication
Affected:< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.0
MagentoCMS
Affected:< 2.4.4= 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 the Adobe Commerce or Magento version
    Check the version by viewing the composer.json file in the project root directory, or log into the admin panel and look at the footer of any page which typically displays the Magento version.
    Affected if The installed version is any of these: < 2.4.4, 2.4.4, 2.4.5, 2.4.6, 2.4.7, or 2.4.8.
  2. Check if Adobe Commerce B2B module is installed and its version
    Run the command 'php bin/magento module:status Magento_Company' to see if the B2B module is enabled, or inspect the composer.lock file for the magento/module-b2b-metapackage version.
    Affected if The B2B module is installed and the version is any of: < 1.3.3, 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.0.
  3. Verify the exact patch level of the installation
    Check the app/etc/config.php file for the installed patch version, or run 'php bin/magento --version' in the command line to get the precise version number including any patch suffixes.
    Affected if The installation shows no patch suffix or a patch version earlier than p11 for 2.4.4, p10 for 2.4.5, p8 for 2.4.6, or p3 for 2.4.7.

You are affected if your Adobe Commerce or Magento installation version falls within the listed vulnerable ranges (2.4.4 through 2.4.8 or B2B versions 1.3.3 through 1.5.0) and you have not applied the corresponding security patches.

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
Upgrade available Upgrade to 1.3.3 / 2.4.4 or later
Fixed in 1.3.32.4.4
Interim mitigation

Apply Adobe security patches for the affected versions (2.4.4-p11, 2.4.5-p10, 2.4.6-p8, 2.4.7-p3, 2.4.8-beta1) or upgrade to a patched version, ensuring all user-supplied form input is properly sanitized and output-encoded.

Recommended fix High confidence

Apply the appropriate security patch (2.4.4-p11, 2.4.5-p10, 2.4.6-p8, or 2.4.7-p3) or upgrade to the latest stable 2.4.8 release when available

  1. 1. Identify your current Adobe Commerce/Magento version in the admin panel under System > Configuration > General > Advanced > Advanced (or via bin/magento --version CLI).
  2. 2. Based on your current version, apply the appropriate security patch: For 2.4.4.x, upgrade to 2.4.4-p11; For 2.4.5.x, upgrade to 2.4.5-p10; For 2.4.6.x, upgrade to 2.4.6-p8; For 2.4.7.x, upgrade to 2.4.7-p3; For 2.4.3 or earlier, upgrade to the minimum affected version (2.4.4) then apply the p11 patch, or directly to the latest stable 2.4.8 release when available.
  3. 3. Backup your database and codebase before applying any upgrade or patch.
  4. 4. Apply the upgrade via Composer: composer require magento/product-community-edition=<version> --no-update (e.g., composer require magento/product-community-edition=2.4.4-p11 --no-update), then run composer update.
  5. 5. After upgrade, clear the cache: bin/magento cache:clean && bin/magento cache:flush.
  6. 6. Reindex all data: bin/magento indexer:reindex.
  7. 7. Verify the upgrade was successful and test critical admin workflows to ensure functionality.
Caveat Minor patch upgrades typically have minimal breaking changes; always test in a staging environment first as custom extensions may require compatibility updates

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 / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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