CVE-2026-47982
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 confidenceA DOM-based Cross-Site Scripting (XSS) vulnerability exists in Adobe Experience Manager versions 6.5.24, LTS SP1, 2026.04 and earlier. The vulnerability allows attackers to manipulate the DOM environment and execute malicious JavaScript within a victim's browser context through a crafted webpage. This issue requires user interaction where the victim must visit the malicious page, and the scope change indicates the attack can impact components beyond the initially 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.
-
Identify installed AEM versionAccess the AEM Web Console Product Information page at /system/console/product or check the version.properties file located in the crx-quickstart directoryAffected if The version displayed is less than 6.5.25.0 or less than 2026.5.0 or equals exactly 6.5
-
Confirm exact version numberRecord the full version string from the AEM about page, including any service pack or hotfix identifiersAffected if The version falls within the affected ranges: < 6.5.25.0, < 2026.5.0, or = 6.5
-
Assess user interaction exposureDetermine if end users can access AEM through web browsers and whether they might be redirected to malicious external pages from AEM contentAffected if Users have browser access to AEM and could be tricked into visiting attacker-controlled webpages that interact with AEM
-
Check for Content Security Policy headersInspect HTTP response headers from AEM pages for the presence of Content-Security-Policy directives using browser developer tools or a HEAD requestAffected if No CSP headers are configured, providing no defense-in-depth against DOM-based XSS
An AEM installation is affected if it runs any version below 6.5.25.0 or below 2026.5.0 (or exactly version 6.5) and users can be socially engineered to visit attacker-controlled webpages that manipulate 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
Fix the vulnerable DOM manipulation code to properly sanitize and validate user input before inserting it into the DOM, and implement or update Content Security Policy headers to mitigate XSS execution. Upgrading to a patched version of AEM when available is recommended.
AEM 6.5.25.0 (for 6.5.x line) or AEM 2026.5.0 (for 2026.x line)
- Backup the current Adobe Experience Manager instance and verify all content is safely stored
- Test the upgrade in a non-production/staging environment before deploying to production
- Upgrade AEM 6.5.x installations to version 6.5.25.0 or later
- Upgrade AEM 2026.x installations to version 2026.5.0 or later
- After upgrade, verify the AEM instance starts successfully and all services are operational
- Test that the DOM-based XSS vulnerability is resolved by validating that user-supplied content in the DOM is properly escaped
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47982 — 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-47982 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