CVE-2026-47989
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 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability where an attacker can manipulate the DOM environment to inject and execute malicious JavaScript within a victim's browser. This is a client-side vulnerability where user-supplied data is read by JavaScript and reflected into the DOM without proper sanitization, requiring the victim to visit a crafted webpage.
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 AEM version via system consoleAccess the AEM System Information console at /system/console/configMgr or check the version.json endpoint at /crx/packmgr/service.jsp?cmd=version. Alternatively, locate the manifest file in the AEM installation directory or check the 'About Adobe Experience Manager' page in the OSGi console.Affected if The displayed version is 6.5.24 or earlier, or 2026.04 or earlier, or shows version 6.5 without a specific service pack version above 24
-
Verify AEM service pack levelIn the AEM Web Console, navigate to the 'Information' section or check the crx/packmgr/service.jsp?cmd=version response. The version string typically follows the format 6.5.x.x where x represents the service pack number.Affected if The service pack number is 24 or lower, or the version string does not indicate 6.5.25.0 or higher
-
Confirm AEM instance type and release lineDetermine whether the instance is on the Long-Term Support (LTS) release track or the quarterly release track. Check the version identifier - LTS versions follow the 6.5.x format while quarterly releases follow the YYYY.MM format (e.g., 2026.04).Affected if The instance is on LTS with version 6.5 (implying 6.5.0 base) or on quarterly release 2026.04 or earlier, and has not been updated to 2026.5.0 or later
-
Assess web interface exposureConfirm that the AEM web interface (author or publish instance) is accessible over HTTP/HTTPS, since this DOM-based XSS requires a victim's browser to interact with the crafted payload through the web interface.Affected if The AEM web interface is accessible and the version check above confirms an affected version
An AEM installation is affected if its version is 6.5.24 or earlier (LTS track), 2026.04 or earlier (quarterly track), or shows as version 6.5 base without an updated service pack, and the web interface is accessible for user interaction.
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 the latest patched version of Adobe Experience Manager (6.5.24+ or the latest LTS/2026.x release). Additionally, implement Content Security Policy (CSP) headers to mitigate XSS execution, and validate all client-side DOM inputs using secure APIs.
Upgrade to AEM 6.5.25.0 or later (LTS line) OR 2026.5.0 or later (2026 release line)
- Identify the current Adobe Experience Manager version in use
- Review the Adobe Experience Manager release notes for version 6.5.25.0 or later (or 2026.5.0+ for the 2026 release line)
- Create a full backup of the AEM instance and content repository
- Test the upgrade in a non-production/staging environment to verify compatibility
- Upgrade the production environment to 6.5.25.0 or later, or 2026.5.0 or later depending on the release line
- Verify that the DOM-based XSS vulnerability (CVE-2026-47989) is remediated by reviewing the fixed version's security patches
- Confirm all custom code and integrations function correctly post-upgrade
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-47989 — 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-47989 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