CVE-2025-24414
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 confidenceAdobe Commerce is affected by a stored Cross-Site Scripting (XSS) vulnerability in multiple versions (2.4.8-beta1 through 2.4.4-p11 and earlier). A low-privileged attacker can inject malicious JavaScript into vulnerable form fields, which persists in the system and executes when other users browse to the affected page, potentially enabling session takeover.
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 installed Adobe Commerce or Magento versionRun command: php bin/magento --version OR check the composer.json file in the project root for the 'version' field under 'require' (e.g., "magento/product-community-edition": "2.4.7")Affected if The installed version matches 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or any version earlier than 2.4.4 (e.g., 2.4.3, 2.4.2) - verify against the affected version list provided.
-
Check if Adobe Commerce B2B extension version is vulnerableRun: php bin/magento module:status Magento_B2b OR inspect composer.json for "magento/module-b2b": "<version>" - note that B2B versions 1.3.3, 1.3.4, 1.3.5, 1.4.2, and 1.5.0 are also affectedAffected if B2B extension version is one of the affected versions listed or earlier than 1.3.3.
-
Confirm access to form inputs where user-supplied data is acceptedReview application for form fields that accept user input and persist data (customer registration, address book, admin-created content, or any custom forms). Check the admin panel under Stores > Attributes > Customer or similar attribute configuration pages.Affected if The application contains form fields that store user input without proper output encoding and are accessible to low-privileged users.
-
Identify if low-privileged user accounts can be created or accessedCheck user role permissions in System > Permissions > User Roles in the admin panel. Verify whether customer accounts or low-level admin users have access to vulnerable form fields.Affected if Low-privileged users (customers or limited admin roles) can access and submit data to the affected form fields.
-
Review application logs for suspicious script injection patternsSearch var/log/exception.log and var/log/system.log for unusual HTML tags (<script>, <img onerror=, javascript:, or encoded characters) in form submission valuesAffected if Logs contain unencoded HTML or JavaScript strings submitted through form fields, indicating potential exploitation attempts.
Your environment is affected if the installed Adobe Commerce or Magento version matches 2.4.4 through 2.4.8 (or earlier) AND low-privileged users can access form fields that accept and display user-submitted data without sanitization.
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 patch or upgrade to a fixed Adobe Commerce version. Additionally, implement output encoding and input validation on affected form fields as a defense-in-depth measure until patching is complete.
Adobe Commerce 2.4.4-p12 / 2.4.5-p11 / 2.4.6-p9 / 2.4.7-p4 (and corresponding B2b patches)
- 1. Identify your current Adobe Commerce (Magento) version by running: bin/magento --version
- 2. Access the Adobe Security Bulletin (helpx.adobe.com) for CVE-2025-24414 to obtain the specific patch file for your version
- 3. For Adobe Commerce 2.4.4: Apply security patch 2.4.4-p12 or later
- 4. For Adobe Commerce 2.4.5: Apply security patch 2.4.5-p11 or later
- 5. For Adobe Commerce 2.4.6: Apply security patch 2.4.6-p9 or later
- 6. For Adobe Commerce 2.4.7: Apply security patch 2.4.7-p4 or later
- 7. For Adobe Commerce B2b: Apply the corresponding Commerce patch (B2b patches are bundled with Commerce patches)
- 8. After applying the patch, clear the Magento cache: bin/magento cache:flush
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24414 — 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-24414 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