CVE-2026-47993
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, LTS SP1, 2026.04 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability where attackers can manipulate the DOM environment to execute malicious JavaScript within a victim's browser session.
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 Adobe Experience Manager installationLocate AEM by checking for the crx-quickstart directory or accessing the AEM welcome page at /libs/granite/core/content/login.html. Confirm AEM is running by accessing the instance.Affected if AEM is installed and accessible
-
Determine installed AEM versionNavigate to /system/console/bundle or check the version file in the AEM installation directory (crx-quickstart/app/etc/version). Compare the version number to the affected ranges.Affected if Version is less than 6.5.25.0, equals 6.5, or is less than 2026.5.0 (if applicable to the deployment model)
-
Check if user-generated content or external input handling is enabledReview AEM configuration for components that accept and render user input in the DOM, such as content fragments, experience fragments, or custom components that manipulate the document object model.Affected if Components that render external or user-supplied content into the DOM without sanitization are active
-
Inspect for DOM manipulation vectorsExamine AEM page source for JavaScript that reads from URL parameters, referrer headers, or other client-side sources and writes directly to innerHTML, document.write, or similar DOM-modifying methods without proper encoding.Affected if DOM manipulation code that uses untrusted input without sanitization is present in active components
-
Look for signs of exploitationReview server access logs and browser developer console for unusual script tags, encoded payloads in request parameters, or evidence of malicious JavaScript execution patterns.Affected if Logs show suspicious requests with script tags, event handlers, or encoded payloads in URL parameters pointing to AEM pages
You are affected if your AEM installation version is less than 6.5.25.0, equals 6.5, or falls below 2026.5.0 in the applicable version model, and your instance renders untrusted input into the DOM without sanitization.
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 as specified in Adobe's official security bulletin.
6.5.25.0 (for AEM 6.5 LTS) or 2026.5.0 (for AEM as a Cloud Service)
- 1. Back up the current Adobe Experience Manager instance, including the database and content repository
- 2. Download Adobe Experience Manager version 6.5.25.0 or 2026.5.0 from the official Adobe distribution portal (helpx.adobe.com)
- 3. Install the service pack or upgrade following Adobe's official documentation for your specific deployment model
- 4. Verify the upgrade was successful by checking the AEM version in the system console (/system/console/configMgr)
- 5. Test the application to confirm functionality remains intact
- 6. Clear browser caches and test for the XSS fix by ensuring the vulnerable DOM manipulation vectors no longer execute arbitrary JavaScript
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47993 — 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-47993 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