dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-27288

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 crafted webpage.

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 confidence

DOM-based Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.24, FP11.7 and earlier. Attackers can manipulate the DOM environment to execute malicious JavaScript within the victim's browser context.

MitigationUpgrade Adobe Experience Manager to a patched version beyond 6.5.24/FP11.7 and implement Content Security Policy (CSP) headers to mitigate client-side XSS execution.

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. Verify Adobe Experience Manager version
    Check the product version in the AEM Welcome page (help > Version Information) or via the system console (system/console/bundles), or inspect the JAR file properties in the crx-quickstart folder
    Affected if The installed AEM version is 6.5.24.0 or earlier (including all 6.5.x versions prior to 6.5.24) or FP11.7 or earlier for the feature pack version
  2. Verify Adobe Experience Manager Screens version
    Check the AEM Screens package version via the system console (system/console/bundles) or look for screens-core JAR in the install folder
    Affected if The installed AEM Screens version is lower than 6.5.11.8
  3. Identify DOM-handling components
    Review custom components, client-side libraries, or third-party integrations that manipulate the DOM using user-supplied input, particularly in cq:editConfig or cq:design_dialog configurations
    Affected if Custom components accept unsanitized user input and inject it directly into the DOM without proper encoding or validation
  4. Check for exposed content editing interfaces
    Audit the publishing instance endpoints and any publicly accessible Editable Templates, Experience Fragments, or Content Services that accept user input and render it client-side
    Affected if Anonymous or low-privilege users can submit content that gets rendered in the browser without server-side output encoding
  5. Review Content Security Policy configuration
    Inspect the Apache Sling main servlet or dispatcher configuration for CSP header rules, looking for 'unsafe-inline' or overly permissive script-src directives
    Affected if CSP headers are missing, not enforced, or contain 'unsafe-inline' which would allow the XSS to execute in victim browsers

A user is affected if their AEM version is 6.5.24.0 or earlier (or AEM Screens below 6.5.11.8) AND the environment contains components or endpoints that render user input directly into the browser DOM without sanitization.

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

Upgrade Adobe Experience Manager to a patched version beyond 6.5.24/FP11.7 and implement Content Security Policy (CSP) headers to mitigate client-side XSS execution.

Recommended fix High confidence

AEM 6.5.24.1+ or AEM Screens 6.5.11.8+

  1. 1. Identify the current Adobe Experience Manager version in your deployment using the AEM Web Console or version information.
  2. 2. For Adobe Experience Manager (AEM) 6.5.x: Upgrade to version 6.5.24.1 or later, which contains the security patch for this DOM-based XSS vulnerability.
  3. 3. For Adobe Experience Manager Screens: Upgrade to version 6.5.11.8 or later.
  4. 4. After upgrading, verify the AEM instance is running correctly by accessing the Welcome page and checking for any error messages.
  5. 5. Test critical workflows in your AEM environment to ensure functionality is preserved after the upgrade.
  6. 6. Clear browser caches and test to confirm the XSS fix is applied and no new vulnerabilities are introduced.
Caveat Standard upgrade risks apply - review Adobe's upgrade documentation for any migration steps or compatibility considerations specific to your version

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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