CVE-2026-48371
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 is 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. Scope is changed.
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 · moderate confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Commerce allows low-privilege attackers to inject malicious JavaScript into vulnerable form fields. When victims browse to pages containing the compromised field, the script executes in their browser. The scope change indicates the vulnerability impacts components beyond the vulnerable form itself.
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.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9= 1.3.3= 1.3.4= 1.4.2= 1.5.2= 1.5.3= 2.4.6= 2.4.7= 2.4.8= 2.4.9>= 1.6.0, < 1.21.0CVSS 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 your Adobe Commerce or Magento installation versionRun the command bin/magento --version or check the composer.json file in your installation root for the magento/product-community-edition version numberAffected if The installed version matches 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9
-
Check if Adobe Commerce B2B module is installedRun bin/magento module:status | grep -i b2b or inspect the app/etc/config.php file for Magento_B2b module entryAffected if The B2B module version is 1.3.3, 1.3.4, 1.4.2, 1.5.2, or 1.5.3 and the core commerce version is also affected
-
Verify Adobe I/O Events version if installedCheck composer.json for adobe/io-events version or run bin/magento module:status | grep -i "IO Events" to confirm the module is presentAffected if Adobe I/O Events version is 1.6.0 or higher but below 1.21.0
-
Inspect form field configurations for input validationReview the form XML configuration files in your theme or module (typically in view/frontend/ui_component or adminhtml areas) and check if the fieldsets used by low-privilege users have proper data-saw attributes for output encodingAffected if Form fields lack proper input validation or output encoding attributes and the application version is in the affected list
-
Search database for suspicious script injectionsQuery the core_config_data table or relevant form-related tables for any <script> tags, javascript: URIs, or on* event handlers stored in form field valuesAffected if Any records contain unsanitized JavaScript payloads in form submission fields
Your environment is affected if you run any of the listed Adobe Commerce, Magento, or Adobe I/O Events versions AND have form fields accessible to low-privilege users that lack proper 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.21.0
Apply Adobe Commerce security patches or update to the latest version. Implement robust input validation and output encoding on all form fields, and enforce a strict Content Security Policy (CSP) to mitigate XSS execution.
Adobe Commerce 2.4.7-p5+ or latest 2.4.x stable; Adobe Commerce B2B 1.4.3-p1+ or latest stable; I/O Events 1.21.0+
- 1. Identify the specific Adobe Commerce, Magento, or I/O Events installation in your environment
- 2. Consult the official Adobe security bulletin at helpx.adobe.com for the complete list of fixed versions for this CVE
- 3. For Adobe Commerce/Magento: Upgrade to the next available patch release (e.g., 2.4.7-p5 or later, or the latest 2.4.x stable release) that includes the security fix
- 4. For I/O Events: Upgrade to version 1.21.0 or later which addresses the vulnerability
- 5. After upgrading, clear all caches (bin/magento cache:clean, bin/magento cache:flush)
- 6. Verify the upgrade was successful by checking the admin panel version information
- 7. Test that the XSS fix is working by attempting to inject script content into form fields that were previously vulnerable
- 8. Ensure all custom code and third-party extensions are still compatible with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48371 — 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-2026-48371 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