CVE-2026-48250
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 (XSS) vulnerability where attackers can manipulate the DOM environment to execute malicious JavaScript in victim's browsers. The vulnerability requires user interaction (victim visiting a crafted webpage) and has a changed scope, 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.
-
Identify installed AEM versionAccess the AEM Web Console (typically at /system/console/config or /crx/packmgr), or check the manifest file in the installation directory. The version is also visible on the Welcome page under 'Adobe Experience Manager'.Affected if The installed version is 6.5.24 or earlier, OR is 6.5.x (any service pack below 6.5.25), OR is 2026.04 or earlier, OR falls below 2026.5.0.
-
Confirm the AEM release lineDetermine whether the installation is on the LTS (Long Term Support) 6.5 track or the 2026 quarterly release track by checking the version string in the About Adobe Experience Manager page.Affected if The instance is on LTS 6.5 without service pack 6.5.25, or is on the 2026 track without reaching 2026.5.0.
-
Review custom client-side code for DOM manipulationInspect any custom front-end JavaScript, HTL templates, or clientlibs under /apps for usage of innerHTML, outerHTML, document.write, eval(), or similar methods that insert unsanitized user-controlled data into the DOM.Affected if Custom code inserts request parameters, URL fragments, or user input directly into the DOM without sanitization.
-
Check for unsanitized query parameter handlingSearch client-side scripts for direct reading of URL parameters (URLSearchParams, location.search) or hash fragments (location.hash) that are rendered into the page without encoding.Affected if The application reads URL data and reflects it into the DOM without proper encoding.
-
Assess Content Security Policy configurationReview the Apache Sling main dispatcher configuration or AEM HTML Library Manager settings for 'Content Security Policy' headers. Check if CSP headers are deployed at the CDN or web server level.Affected if No CSP headers are defined, or CSP allows unsafe-inline/unsafe-eval which would not mitigate DOM XSS.
You are affected if your AEM version is below 6.5.25.0 on the LTS track or below 2026.5.0 on the 2026 track, AND your instance has custom client-side code that manipulates the DOM with unsanitized user input.
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 to a patched version of Adobe Experience Manager or implement Content Security Policy (CSP) headers to mitigate XSS execution. Organizations should also review and sanitize any user-controlled data that gets rendered in the DOM.
6.5.25.0 (LTS) or 2026.5.0 (newer release track)
- Upgrade Adobe Experience Manager to version 6.5.25.0 or later for the LTS release track
- Alternatively, upgrade to version 2026.5.0 or later for the newer release track
- After upgrading, verify that the DOM-based XSS vulnerability is resolved by testing the previously vulnerable endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48250 — 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-48250 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