CVE-2026-48266
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 Experience Manager versions 6.5.24, LTS SP1, 2026.04 and earlier are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability. An attacker could exploit this issue by manipulating the DOM environment to execute malicious JavaScript within the context of the victim's browser. Exploitation of this issue requires user interaction in that a victim must visit a crafted webpage. 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 · high confidenceAdobe Experience Manager versions 6.5.24, LTS SP1, 2026.04 and earlier contain a DOM-based Cross-Site Scripting vulnerability where malicious JavaScript can be injected through manipulation of the DOM environment. This requires user interaction where a victim must visit a crafted webpage, and the scope has changed indicating impact beyond the vulnerable component.
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< 6.5.25.0< 2026.5.0= 6.5CVSS 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.
-
Check installed Adobe Experience Manager versionAccess the AEM welcome page at /libs/granite/core/content/login.html or use the system console at /system/console/bundles and locate the version information in the About Adobe Experience Manager sectionAffected if The version displayed is 6.5.24 or earlier, 6.5.x LTS SP1, or 2026.04 or earlier (versions below 6.5.25.0 or 2026.5.0)
-
Verify AEM author or publish instance is network accessibleConfirm whether the AEM instance is accessible over HTTP/HTTPS to users beyond the internal network, as the XSS requires victims to visit crafted webpagesAffected if The instance is exposed to untrusted networks where attackers could serve malicious pages to victims
-
Identify custom AEM components handling user-generated contentReview components under /apps that accept user input and render output, particularly those using JavaScript or DOM manipulation methods such as innerHTML, outerHTML, or document.writeAffected if Custom components exist that render unsanitized user input directly into the HTML DOM without output encoding
-
Inspect Content Security Policy configurationNavigate to /system/console/configMgr and locate the Adobe Granite CSRF Filter and Content Security Policy configurations, or check /etc/clientlibs for CSP headersAffected if CSP is not configured or allows unsafe-inline scripts, providing no defense-in-depth against DOM XSS
-
Review Experience Fragments and Coral UI componentsCheck /libs/cq/experience-fragments and /libs/cq/gui/components for components that manipulate the DOM based on URL parameters or user-provided contentAffected if These components accept and render URL parameters or user content without proper sanitization in the DOM context
You are affected if your AEM version is 6.5.24 or earlier, 6.5.x LTS SP1, or 2026.04 or earlier AND the vulnerable DOM manipulation points are accessible to users who could be tricked into visiting attacker-controlled 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 · scoped6.5.25.02026.5.0
Upgrade Adobe Experience Manager to the vendor-patched version beyond 6.5.24, LTS SP1, and 2026.04. Implement Content Security Policy headers as an additional defense-in-depth measure for DOM XSS.
6.5.25.0 (for 6.5.x line) or 2026.5.0 (for 2026.x line)
- 1. Identify the current Adobe Experience Manager version by checking the product about page or system console
- 2. Plan the upgrade - schedule a maintenance window and review Adobe's upgrade documentation for your release line
- 3. Create a full backup of the AEM instance including the repository, configuration, and any custom code
- 4. Test the upgrade in a non-production environment first to identify any compatibility issues
- 5. Upgrade AEM 6.5.x installations to version 6.5.25.0 or later
- 6. OR upgrade AEM as a Cloud Service / 2026.x installations to version 2026.5.0 or later
- 7. After upgrade, verify the XSS vulnerability is resolved by testing the previously vulnerable endpoint
- 8. Deploy the validated upgrade to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48266 — 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-48266 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