CVE-2025-24416
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 · uneditedAdobe 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 confidenceStored XSS vulnerability in Adobe Commerce allowing low-privileged attackers to inject malicious JavaScript into form fields. When victims browse affected pages, the script executes in their browsers, enabling session takeover and high confidentiality/integrity impact.
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< 2.4.4= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.0< 2.4.4= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine Adobe Commerce or Magento versionLocate the composer.json file in the Magento root directory and look for the version entry under 'require' -> 'magento/product-community-edition' or 'magento/product-enterprise-edition'. Alternatively, log into the Admin panel and navigate to System > Settings > About the System to view the version.Affected if The installed version matches 2.4.4, 2.4.5, 2.4.6, 2.4.7, or 2.4.8, or is earlier than 2.4.4 (any version before 2.4.4).
-
Determine Adobe Commerce B2B version if installedCheck composer.json for 'magento/module-b2b' under the 'require' section. If present, note the version number. Alternatively, check the app/code/Magento/B2bDirectory directory existence or run 'php bin/magento module:status' to list enabled modules.Affected if B2B module is installed with version 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.0, or version earlier than 1.3.3.
-
Verify low-privilege user access to form fieldsLog into the Admin panel with a low-privilege (non-admin) account and identify accessible form fields, particularly in customer-facing or user profile sections. Check the Roles and Permissions configuration under System > Permissions > User Roles to determine which roles have access to form input pages.Affected if Low-privilege users can access and submit data through any form fields in the application.
-
Inspect stored form data for unsanitized inputQuery the database tables that store form submissions, such as customer_entity, quote_address, or custom form tables, to inspect whether input data contains unescaped HTML or script tags. Use SQL: SELECT * FROM customer_entity WHERE email LIKE '%<script%' OR firstname LIKE '%<script%'.Affected if Stored data contains raw HTML or JavaScript tags that would execute when rendered in the admin or user interface.
You are affected if your Adobe Commerce or Magento installation version is 2.4.4 through 2.4.8 or any version earlier than 2.4.4, combined with the presence of accessible form fields that low-privilege users can populate.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.3.32.4.4
Update Adobe Commerce to patched versions (2.4.7-p4, 2.4.6-p9, 2.4.5-p11, 2.4.4-p12 or later) per Adobe security bulletin APSB25-14. Implement output encoding on affected form fields as temporary mitigation if patching is delayed.
Adobe Commerce 2.4.7-p3 (or latest 2.4.x patch); Adobe Commerce B2B 1.4.0 or later
- 1. Backup your Adobe Commerce/Magento database and files
- 2. For Adobe Commerce (Magento Open Source) users: Upgrade to version 2.4.7-p3 or later (or the latest 2.4.x patch)
- 3. For Adobe Commerce with B2B users: Upgrade to version 1.4.0 or later which includes the Commerce 2.4.7-p3 patches
- 4. Clear all caches after upgrade: bin/magento cache:flush
- 5. Re-index all data: bin/magento indexer:reindex
- 6. Verify the upgrade by checking the admin panel and frontend for proper functionality
- 7. Test the specific form fields mentioned in the vulnerability to confirm the XSS fix is effective
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24416 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24416 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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