dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-34623

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 6.5.11.8 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, FP11.7 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 specially crafted web page.

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 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability where attackers can manipulate the DOM environment to execute malicious JavaScript within the context of a victim's browser. Exploitation requires user interaction, specifically that the victim must visit a specially crafted web page.

MitigationImplement output encoding and input validation for all user-controlled DOM elements, deploy Content Security Policy (CSP) headers to restrict script execution, and upgrade to the patched AEM version (6.5.25 or later, FP11.8 or later).

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.24.0
Experience Manager ScreensApplication
Affected:< 6.5.11.8

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. Check Adobe Experience Manager version
    Access the AEM Web Console at /system/console/configMgr or check the quickstart JAR file name for the version number (e.g., aem-quickstart-6.5.24.0.jar). Alternatively, check the version manifest in the crx-quickstart folder.
    Affected if The installed version is 6.5.24.0 or earlier, or the Feature Pack (FP) version is 11.7 or earlier.
  2. Check Adobe Experience Manager Screens version
    In AEM, navigate to the Screens player or check the version through the AEM package manager. The Screens package is typically installed as com.adobe.aem.screens:screens-core.
    Affected if The installed AEM Screens version is lower than 6.5.11.8.
  3. Confirm the instance is exposed to untrusted web content
    Identify whether the AEM instance renders or displays user-supplied content in web pages without sanitization. Check if external or untrusted content is displayed in any published pages or components.
    Affected if The AEM instance allows rendering of untrusted or unsanitized content in web pages accessible to users.
  4. Verify if Content Security Policy headers are enforced
    Inspect HTTP response headers on published AEM pages using browser developer tools or a web proxy. Look for CSP headers in the response.
    Affected if No strict Content Security Policy (CSP) headers are set, allowing inline scripts or untrusted script sources to execute.

You are affected if your AEM version is 6.5.24.0 or earlier (or FP11.7 or earlier) AND your instance renders untrusted content in web pages without proper sanitization or CSP protection.

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.11.8 or later
Fixed in 6.5.11.8
Interim mitigation

Implement output encoding and input validation for all user-controlled DOM elements, deploy Content Security Policy (CSP) headers to restrict script execution, and upgrade to the patched AEM version (6.5.25 or later, FP11.8 or later).

Recommended fix Moderate confidence

AEM 6.5.24.1+ (for AEM); AEM Screens 6.5.11.8+ (for Screens)

  1. 1. Identify the exact Adobe Experience Manager (AEM) product and version currently deployed (AEM Assets, AEM Sites, or AEM Screens).
  2. 2. For AEM (non-Screens): Upgrade to version 6.5.24.1 or later, as version 6.5.24.0 and earlier are affected by this DOM-based XSS vulnerability.
  3. 3. For AEM Screens: Upgrade to version 6.5.11.8 or later, as versions prior to 6.5.11.8 are affected.
  4. 4. After upgrading, verify the AEM instance starts successfully and all critical workflows function normally.
  5. 5. Test the fix by confirming that user-supplied content in the DOM is properly sanitized and no unsanitized JavaScript execution occurs.
  6. 6. Review Adobe's official security bulletin for any additional required hotfixes or configuration changes.
Caveat Standard upgrade risks apply - test in staging environment before production deployment, as custom code or integrations may require updates for compatibility with newer AEM versions.

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
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34623 — 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-34623 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