CVE-2026-47946
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 in Adobe Experience Manager allows attackers to inject malicious JavaScript through manipulation of the DOM environment. The vulnerability affects versions 6.5.24, LTS SP1, 2026.04 and earlier, requiring user interaction where victims must visit a crafted webpage. The scope is changed, indicating the vulnerability can impact resources 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.
-
Verify installed AEM versionAccess the AEM System Information console at /system/console/status-productinfo or check the version.properties file in the crx-quickstart folder. Also check via the AEM Welcome page 'Version' link.Affected if The installed version is 6.5.x at 6.5.24 or earlier, OR the version is 2026.5.0 or any version prior to 2026.5.0.
-
Identify custom components handling DOM manipulationReview the codebase for custom OSGi bundles, HTL components, or client-side JavaScript that reads URL parameters, referrer headers, or user-supplied content and directly injects it into the DOM via innerHTML, document.write, or similar methods.Affected if Custom components exist that use unsafe DOM manipulation methods with unsanitized user input.
-
Check for vulnerable DOM sink usage in AEM componentsSearch source code repositories for patterns like element.innerHTML =, element.outerHTML =, document.write(, jQuery html(), or similar DOM sinks that accept raw request parameters or query string values.Affected if Code patterns exist where user-supplied parameters are assigned directly to DOM properties without sanitization.
-
Audit AEM forms and query parameter handlingExamine any custom AEM components, pages, or endpoints that process URL query parameters or form submissions and render output to the page without proper encoding.Affected if Custom AEM components accept and render URL parameters or form data directly to the HTML page.
The environment is affected if the installed AEM version is 6.5.24 or earlier, or any version below 2026.5.0, AND custom components that manipulate the DOM with unsanitized user input are deployed.
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 version beyond 6.5.24, LTS SP1, or 2026.04. Additionally, implement output encoding and input validation for any client-side code that manipulates the DOM to prevent malicious script execution.
6.5.25.0 or later for 6.5.x LTS line; 2026.5.0 or later for newer release line
- Review the Adobe Experience Manager upgrade documentation at helpx.adobe.com for your current version
- Plan and schedule maintenance window for the upgrade process
- Back up your AEM instance including repository, database, and configuration files
- Test the upgrade in a non-production environment before applying to production
- Upgrade AEM 6.5.x instances to version 6.5.25.0 or later
- Upgrade 2026.04 and earlier instances to version 2026.5.0 or later
- Verify the upgrade was successful by checking the AEM version in the About Adobe Experience Manager page
- Validate that the XSS vulnerability is remediated by confirming the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.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 $6,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47946 — 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-47946 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