CVE-2026-47983
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 · moderate confidenceAdobe Experience Manager versions 6.5.24, LTS SP1, 2026.04 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability. Attackers can manipulate the DOM environment through a crafted webpage to execute malicious JavaScript in the victim's browser. User interaction is required (victim must visit the malicious page), and the CVSS scope is 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.
-
Determine installed AEM versionAccess the AEM system information console at /system/console/bundles or check the 'About Adobe Experience Manager' page in the AEM Welcome screen. Alternatively, check the version.properties file in the crx-quickstart folder.Affected if The installed version is 6.5.x before 6.5.25.0, or 2026.x before 2026.5.0, or specifically version 6.5 (meaning any 6.5.x release)
-
Identify AEM release trackVerify whether the installation is on the standard 6.5 LTS release track or the newer 2026 release track by reviewing the version number format from the system information.Affected if The version matches the pattern 6.5.x (where x is any build before 6.5.25) or 2026.x (where x is any build before 2026.5.0)
-
Confirm DOM XSS exposureReview web application logs and browser console for any suspicious script execution or unexpected DOM manipulation occurring from user-supplied input in the AEM interface.Affected if JavaScript execution is observed in the browser console originating from AEM pages handling user-controlled content without proper sanitization
You are affected if your AEM installation is any version before 6.5.25.0 on the 6.5 LTS track, or any version before 2026.5.0 on the 2026 track, and your users can be tricked into visiting attacker-controlled webpages.
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 Adobe Experience Manager version. Until then, implement Content Security Policy (CSP) headers to mitigate XSS execution and educate users about avoiding untrusted links.
6.5.25.0 or later (6.5.x line); 2026.5.0 or later (2026.x line)
- 1. Back up your current Adobe Experience Manager instance including content and configuration
- 2. Review Adobe's upgrade documentation for your specific version path
- 3. Download Adobe Experience Manager 6.5.25.0 or later (or 2026.5.0 or later for the newer release line) from the Adobe distribution center
- 4. Run the upgrade following Adobe's standard upgrade procedures
- 5. After upgrade, verify that the AEM instance starts successfully
- 6. Test critical workflows to ensure functionality is preserved
- 7. Validate the XSS fix by checking that the vulnerable DOM manipulation vectors are no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47983 — 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-47983 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