CVE-2026-47987
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 is affected by a DOM-based Cross-Site Scripting (XSS) vulnerability in versions 6.5.24, LTS SP1, 2026.04 and earlier. The vulnerability allows attackers to manipulate the DOM environment to inject and execute malicious JavaScript within the victim's browser session, with scope changed to affect components beyond the vulnerable one.
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.
-
Determine Adobe Experience Manager versionAccess the AEM Welcome page and click 'Information' > 'About Adobe Experience Manager', or navigate directly to /libs/granite/core/content/about.html to view the product versionAffected if The displayed version is below 6.5.25.0, is version 6.5.x below 2026.5.0, or is an older release like 6.5.24, LTS SP1, or 2026.04
-
Identify the exact AEM release typeCheck the version details from the About page to determine if it is a standard 6.5.x release, an LTS Service Pack (SP) release, or a 2026.x quarterly releaseAffected if The release is the standard 6.5.x line (any version before 6.5.25.0), an LTS Service Pack version, or falls within the 2026.x quarterly releases up to and including 2026.04
-
Verify the product version in AEM system informationNavigate to the AEM Web Console (System Information) at /system/console/systeminformation or check the version.properties file in the AEM installation directory under crx-quickstart/Affected if The version number shown is lower than 6.5.25.0 for the 6.5 line, or lower than 2026.5.0 for the quarterly release line, indicating the patch is not applied
-
Confirm the DOM XSS attack surface existsReview AEM component configurations and custom client libraries that process user-supplied input into the DOM. Check for any custom components using JavaScript that manipulates the DOM without proper sanitizationAffected if Custom or third-party components that render user-controlled data directly into the browser DOM are present and accessible without authentication, making XSS exploitation possible
You are affected if your installed AEM version is any release before 6.5.25.0 in the 6.5.x line, any LTS Service Pack version, or any 2026.x release up to and including 2026.04, and your instance exposes components that render unsanitized input into the DOM.
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 a patched version beyond 6.5.24, LTS SP1, and 2026.04. Additionally, implement output encoding and input validation on client-side code that manipulates the DOM to prevent injection of untrusted data.
AEM 6.5.25.0 or later for 6.5.x releases; AEM 2026.5.0 or later for 2026.x releases
- 1. Identify the current Adobe Experience Manager version by navigating to the AEM System Information console or checking the version.properties file
- 2. If running AEM 6.5.x version prior to 6.5.25.0, plan upgrade to 6.5.25.0 or later
- 3. If running AEM 2026.x version prior to 2026.5.0, plan upgrade to 2026.5.0 or later
- 4. Review Adobe's official upgrade documentation for AEM for step-by-step upgrade procedures
- 5. Perform a complete backup of the AEM repository (segment store) and database before upgrading
- 6. Test the upgrade in a non-production environment first
- 7. Execute the upgrade following Adobe's recommended practices
- 8. Verify the upgrade was successful and the AEM instance is functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47987 — 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-47987 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