CVE-2025-24428
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.
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 contains a stored Cross-Site Scripting (XSS) vulnerability where low-privileged attackers can inject malicious JavaScript into vulnerable form fields. The malicious script persists in the system and executes when victims browse to pages containing the affected fields, allowing attackers to steal session cookies, perform actions as the victim, or deface content.
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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Adobe Commerce or Magento versionCheck the composer.json file in the Magento root directory for the 'version' field, or run the CLI command 'php bin/magento --version' to retrieve the installed versionAffected if The installed version matches < 2.4.4, = 2.4.4, = 2.4.5, = 2.4.6, = 2.4.7, or = 2.4.8
-
Identify Adobe Commerce B2B versionCheck the composer.json file for the 'magento/module-b2b' package version, or list installed packages via 'composer show magento/module-b2b'Affected if The B2B module version matches < 1.3.3, = 1.3.3, = 1.3.4, = 1.3.5, = 1.4.2, or = 1.5.0
-
Verify if customer account registration is enabledNavigate to Stores > Configuration > Customers > Customer Configuration > Account Creation Options, or inspect the database table 'customer_entity' for recent low-privilege user recordsAffected if Customer registration is enabled and low-privilege user accounts exist in the system
-
Inspect stored form data for malicious scriptsQuery database tables that store form input (such as customer_address_entity, quote_address, or custom address attributes) for suspicious HTML or script tags using: SELECT * FROM customer_address_entity WHERE additional_data LIKE '%<script%' OR additional_data LIKE '%javascript:%'Affected if Any records contain unsanitized script tags or event handler attributes in form fields
You are affected if your Adobe Commerce or Magento version falls within the listed vulnerable ranges AND low-privileged user account creation is enabled, allowing attackers to inject malicious scripts into form fields.
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 available security patches or upgrade to a non-vulnerable Adobe Commerce version (beyond 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11). As a temporary measure, implement strict input validation and output encoding on all form fields, particularly those accessible to low-privileged users.
Upgrade to latest patch level on your current branch (2.4.4-p11+, 2.4.5-p10+, 2.4.6-p8+, or 2.4.7-p3+) or migrate to 2.4.8 stable when available
- 1. Identify the current Adobe Commerce/Magento version by checking the admin panel or running `php bin/magento --version`
- 2. Determine the appropriate upgrade path based on your current version branch
- 3. Create a full backup of the production database and files before proceeding
- 4. Test the upgrade in a staging environment that mirrors production
- 5. Upgrade to the appropriate patched version: For 2.4.4 branch, upgrade to 2.4.4-p11 or later. For 2.4.5 branch, upgrade to 2.4.5-p10 or later. For 2.4.6 branch, upgrade to 2.4.6-p8 or later. For 2.4.7 branch, upgrade to 2.4.7-p3 or later
- 6. After upgrade, clear caches: `php bin/magento cache:flush`
- 7. Re-index all data: `php bin/magento indexer:reindex`
- 8. Verify the upgrade by checking the version and testing the affected form fields for proper input sanitization
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24428 — 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-24428 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