dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-34692

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 6.5.25.0 / 2026.5.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Adobe 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 confidence

Adobe Experience Manager versions 6.5.24, LTS SP1, 2026.04 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability where user-supplied input is dynamically inserted into the DOM without proper sanitization, allowing arbitrary JavaScript execution in victim's browser. The vulnerability requires user interaction (visiting a crafted page) and has a changed scope, potentially impacting components beyond the vulnerable one.

MitigationUpgrade AEM to version 6.5.25 or later (or the appropriate patched 2026.x version). Additionally, implement Content Security Policy (CSP) headers to mitigate client-side XSS execution and audit affected AEM components for proper input sanitization before DOM manipulation.

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
Experience ManagerApplication
Affected:< 6.5.25.0< 2026.5.0= 6.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed AEM version
    Access the AEM System Information console at /system/console/info or check the version.properties file in the AEM installation directory to retrieve the exact version number
    Affected if The version number is less than 6.5.25.0, less than 2026.5.0, or equals 6.5 (LTS SP1)
  2. Confirm AEM web interface is exposed
    Verify that the AEM web authoring interface (CQ5/AEM author instance) is accessible over HTTP/HTTPS to external or internal users
    Affected if The AEM web interface is accessible and allows user content rendering through web pages
  3. Check for unauthenticated content access
    Review AEM dispatcher or web server configuration to determine if unauthenticated users can access content pages that render user-supplied input in the DOM
    Affected if Content pages are accessible without authentication and process input that could be reflected in the HTML/DOM
  4. Identify DOM input sinks in custom components
    Review custom AEM components or templates that use JavaScript to process and render user input directly into the DOM without proper sanitization
    Affected if Custom components exist that render unsanitized user input into the browser DOM

Your environment is affected if the installed AEM version is 6.5.24 or earlier, 6.5 (LTS SP1), or any version prior to 2026.5.0, and the web interface is accessible to users who could be tricked into visiting malicious pages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.5.25.0 / 2026.5.0 or later
Fixed in 6.5.25.02026.5.0
Interim mitigation

Upgrade AEM to version 6.5.25 or later (or the appropriate patched 2026.x version). Additionally, implement Content Security Policy (CSP) headers to mitigate client-side XSS execution and audit affected AEM components for proper input sanitization before DOM manipulation.

Recommended fix High confidence

6.5.25.0 or 2026.5.0 or later

  1. Verify current Adobe Experience Manager version in use (check /system/console or About page)
  2. Review Adobe Experience Manager upgrade documentation for your deployment type
  3. Plan upgrade considering 6.5.25.0 or 2026.5.0 as target versions
  4. Create full backup of AEM instance including repository, database, and configurations
  5. Test upgrade in non-production environment before deploying to production
  6. Execute upgrade following Adobe's official upgrade procedures
  7. Validate all custom code, integrations, and workflows post-upgrade
  8. Verify the XSS vulnerability is resolved by testing for proper DOM sanitization
Caveat Review Adobe's upgrade notes for potential compatibility impacts with custom code and integrations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34692 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34692 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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