CVE-2025-24417
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability in Adobe Commerce allows low-privileged authenticated users to inject malicious JavaScript into form fields. When administrators or other users view the compromised data in their browsers, the injected scripts execute, potentially enabling session hijacking and unauthorized actions.
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.
-
Identify the installed Adobe Commerce or Magento versionCheck the version.php file in app/etc/ or run: bin/magento --version from the command lineAffected if The version is 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or any version prior to 2.4.4
-
Check if Adobe Commerce B2B module is installed and identify its versionRun: composer show magento/module-b2b 2>/dev/null or check composer.json for the B2B module versionAffected if B2B module version is 1.3.3, 1.3.4, 1.3.5, 1.4.2, 1.5.0, or any version prior to 1.3.3
-
Verify if low-privileged user accounts exist with form submission accessNavigate to Admin panel, check for customer or low-role user accounts that have access to form input fields (such as customer attributes, product reviews, or custom form fields)Affected if Low-privileged authenticated users can submit or edit data in form fields that lack input validation
-
Inspect form field configuration for output encodingReview the code or template files handling form submissions in the affected areas, specifically looking for missing htmlEscape or escapeHtml methods on user-controlled fieldsAffected if Form fields accept user input without proper sanitization or output encoding before display in admin dashboard
-
Confirm the vulnerable form submission endpoints are accessibleTest accessing form submission points (such as customer account creation, review submission, or custom form handlers) using a low-privileged user accountAffected if Low-privileged users can submit data to forms that later display unsanitized content to administrators
You are affected if your installed Adobe Commerce or Magento version falls within 2.4.4 through 2.4.8 (or any version below 2.4.4) AND low-privileged users have access to form fields without proper input validation or output encoding.
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
Apply vendor patches or upgrade to non-vulnerable versions (2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and later). Additionally, implement output encoding and input validation on all user-controlled form fields.
2.4.4-p11 / 2.4.5-p10 / 2.4.6-p8 / 2.4.7-p3 (or latest 2.4.x release)
- 1. Verify the current Adobe Commerce/Magento version by running: php bin/magento --version
- 2. Review the Adobe Commerce release notes at helpx.adobe.com for the appropriate security patch (SUPEE or quality patch) corresponding to your version
- 3. For Adobe Commerce 2.4.4: Upgrade to 2.4.4-p11 or later by running: composer require magento/product-community-edition=2.4.4-p11 --no-update, then composer update
- 4. For Adobe Commerce 2.4.5: Upgrade to 2.4.5-p10 or later by running: composer require magento/product-community-edition=2.4.5-p10 --no-update, then composer update
- 5. For Adobe Commerce 2.4.6: Upgrade to 2.4.6-p8 or later by running: composer require magento/product-community-edition=2.4.6-p8 --no-update, then composer update
- 6. For Adobe Commerce 2.4.7: Upgrade to 2.4.7-p3 or later by running: composer require magento/product-community-edition=2.4.7-p3 --no-update, then composer update
- 7. After upgrading, clear the cache: php bin/magento cache:clean
- 8. Reindex the catalog: php bin/magento indexer:reindex
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24417 — 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-24417 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