CVE-2025-24413
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 attackers to inject malicious JavaScript into form fields. The malicious payload is stored in the database and executes when administrators or other users view the affected pages, enabling session hijacking and privilege escalation.
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/Magento installed versionRun the CLI command: php bin/magento --version or check the composer.json file in the installation root for the magento/product-community-edition or magento/product-enterprise-edition version entryAffected if The version matches one of the affected ranges: Adobe Commerce and Magento 2.4.4 through 2.4.8 (any build within these versions), or Adobe Commerce B2b versions 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.0
-
Identify stored XSS payloads in databaseQuery the database tables that store form input data. Look for common XSS patterns in fields that accept user input, such as: <script, javascript:, onload=, onerror=, img src=javascript. Example SQL: SELECT * FROM cms_page WHERE content LIKE '%<script%' OR content LIKE '%javascript:%'Affected if Malicious script tags or event handlers are found stored in form-related database tables that get rendered in admin-facing pages
-
Review admin activity logs for injection attemptsCheck var/log/exception.log, var/log/debug.log, and any security audit logs for entries containing XSS patterns like <script, alert(, document.cookie, or base64-encoded payloads in form submission parametersAffected if Logs show recent injection attempts with XSS payloads targeting form fields, indicating active exploitation or probing
-
Inspect form field input validation configurationExamine the adminhtml layout XML files and form field configurations in app/code for the fields involved. Check if the fields have proper validation rules defined in di.xml or ui_component data sources, specifically looking for input validation that would sanitize or escape HTML entitiesAffected if Form fields lack server-side input validation or output encoding is not applied, allowing raw HTML/script content to be stored and rendered
You are affected if your installed Adobe Commerce or Magento version is 2.4.4 through 2.4.8 (any build) and your database contains unsanitized script payloads in form fields that render on admin pages.
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 the vendor patches for versions 2.4.4-p11, 2.4.5-p10, 2.4.6-p8, 2.4.7-p3 or upgrade to the latest stable release. Implement input validation and output encoding on all form fields as a compensating control.
Apply the latest security patch for your respective version line (e.g., 2.4.4-p12+, 2.4.5-p11+, 2.4.6-p9+, 2.4.7-p4+, or upgrade to 2.4.8 stable)
- 1. Identify the current Adobe Commerce or Magento version by running: php bin/magento --version or checking the composer.json file
- 2. For Adobe Commerce 2.4.4: Apply patch version 2.4.4-p12 or later via composer update (e.g., composer require magento/product-community-edition=2.4.4-p12 --no-update)
- 3. For Adobe Commerce 2.4.5: Apply patch version 2.4.5-p11 or later
- 4. For Adobe Commerce 2.4.6: Apply patch version 2.4.6-p9 or later
- 5. For Adobe Commerce 2.4.7: Apply patch version 2.4.7-p4 or later
- 6. For Adobe Commerce 2.4.8: Update to the stable 2.4.8 release or later
- 7. Run composer update to install the patched version
- 8. Clear the cache: php bin/magento cache:flush
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24413 — 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-24413 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