CVE-2025-24410
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 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 pages containing the compromised fields, the malicious script executes in their browsers, 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.
-
Check Adobe Commerce or Magento installed versionRun command: php bin/magento --version or check the version in Admin panel under System > Settings > General > Advanced > Admin > Admin Base URL section, or look at composer.json for the magento/product-community-edition or magento/product-enterprise-edition version entryAffected if The installed version is less than 2.4.4; or equals 2.4.4, 2.4.5, 2.4.6, 2.4.7, or 2.4.8 (including any B2B extension versions matching the affected list)
-
Check Adobe Commerce B2B extension versionRun command: php bin/magento module:status Magento_B2b or check composer.json for magento/module-b2b version. Alternatively, look in app/etc/config.php for the B2B module versionAffected if The B2B extension version is less than 1.3.3; or equals 1.3.3, 1.3.4, 1.3.5, 1.4.2, or 1.5.0
-
Verify if low-privileged user accounts existCheck Admin panel under System > Permissions > Users to see if there are any users with limited (non-admin) roles, or query the admin_user table in the database and cross-reference with the authorization_role table to identify non-admin role assignmentsAffected if There are authenticated users with low-privileged roles (such as customers, limited catalog managers, or custom non-admin roles) who can access form fields in the application
-
Identify form fields that accept user input and are displayed to othersReview custom modules or third-party extensions that add form fields visible to other users (such as customer attributes, company user fields for B2B, or custom form builders). Check the database tables for any custom EAV attributes or extension attributes that store user-supplied valuesAffected if The application contains form fields that accept input from low-privileged users and are rendered on pages viewed by administrators or other users without proper output encoding
You are affected if your Adobe Commerce or Magento version falls within the affected ranges AND low-privileged authenticated users have access to form fields that are displayed to other users 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-provided security patches for the affected 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). Validate and sanitize all user-supplied input in form fields, and implement output encoding to prevent XSS execution.
Upgrade to Adobe Commerce 2.4.7-p3 or later (or the latest 2.4.x patch release)
- 1. Verify your current Adobe Commerce/Magento version by checking the composer.json file or the admin panel.
- 2. Review the Adobe Commerce Security Patch Bulletin (referenced at helpx.adobe.com) for the complete list of fixed versions.
- 3. Plan the upgrade during a maintenance window as the upgrade process requires putting the store in maintenance mode.
- 4. Create a full backup of your database and files before proceeding.
- 5. Update your composer.json to point to the target fixed version (e.g., 2.4.7-p3 or later).
- 6. Run composer update to fetch the new packages.
- 7. Clear the Magento cache and regenerate the dependency injection configuration.
- 8. Test the upgrade in a staging environment before applying to production.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24410 — 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-24410 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