CVE-2026-47985
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 confidenceDOM-based Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.24, LTS SP1, 2026.04 and earlier. Attackers can manipulate the DOM environment to execute malicious JavaScript within the victim's browser. Exploitation requires user interaction where a victim must visit a crafted webpage. The scope change indicates the vulnerability affects resources outside the vulnerable component's origin.
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/configMgr) or check the product.xml file in the installation directory. Alternatively, run the version check endpoint: curl -u admin:password http://localhost:4502/crx/packmgr/service.jsp?cmd=versionAffected if The displayed version is 6.5.x where x is less than 25, or falls below 2026.5.0, or shows as exactly 6.5 (the LTS release)
-
Confirm AEM edition and release lineCheck whether the installation is the Long Term Support (LTS) 6.5 line or the newer 2026 release cadence. This determines which version threshold applies. Query the crx-quickstart folder for manifest files or check /libs/granite/core/content/login.json for version details.Affected if The installation is on the 6.5 LTS track prior to 6.5.25.0, or on the 2026 track prior to 2026.5.0, or is the base 6.5 release
-
Verify if client-side DOM manipulation is in useReview custom AEM components, Sightly/HTL templates, and client-side JavaScript files for direct manipulation of the DOM using user-supplied data. Look for patterns like innerHTML, outerHTML, or document.write() with data from URL parameters, referrer headers, or cookies.Affected if The environment contains custom components or client-side scripts that directly insert unsanitized user input into the DOM without proper escaping or validation
-
Inspect Content Security Policy configurationCheck the Apache Sling servlet filter configuration or the OSGi web console for CSP header settings. Look for CSP filter configurations at /system/console/configMgr/com.adobe.granite.csp.impl.CSPFilter or review web.xml for custom CSP implementations.Affected if No CSP headers are configured, or the policy allows unsafe-inline scripts, which would permit the DOM XSS to execute malicious JavaScript
Your environment is affected if the installed AEM version matches 6.5.x below 6.5.25.0, 6.5 base LTS, or any version below 2026.5.0, AND your application exposes DOM-manipulating code that processes untrusted input client-side.
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 latest patched version. Additionally, implement Content Security Policy (CSP) headers and ensure proper input sanitization to mitigate DOM-based XSS risks.
AEM 6.5.25.0 (LTS) or AEM 2026.5.0
- 1. Identify the current Adobe Experience Manager deployment version and branch (6.5.x LTS or 2026.x)
- 2. For AEM 6.5.x LTS deployments: Upgrade to version 6.5.25.0 or later
- 3. For AEM 2026.x deployments: Upgrade to version 2026.5.0 or later
- 4. Test the upgrade in a non-production environment before deploying to production
- 5. Review Adobe's official release notes and migration guidelines for the target version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation20.0 h
- Testing10.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47985 — 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-47985 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