dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-47935

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, and 2026.04 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability. Attackers can manipulate the DOM environment through a crafted webpage to execute malicious JavaScript in the victim's browser. This is a reflected XSS requiring user interaction where the victim must visit the attacker's malicious page.

MitigationApply the vendor patch for CVE-2026-47935 to the affected AEM installation. Until patched, restrict user access to untrusted external sites and implement Content Security Policy (CSP) headers to mitigate 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.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 the installed AEM version
    Access the AEM Welcome page, or append '/libs/cq/core/content/info.xml' to your AEM base URL, or check the 'About Adobe Experience Manager' section in the system console
    Affected if The version displayed is 6.5.24 or lower, or falls within the 6.5.x LTS SP1 line before 6.5.25.0, or is 2026.04 or lower before the 2026.5.0 release
  2. Verify the exact 6.5.x release number
    If running a 6.5.x release, confirm the full version number from the same version information endpoint used in step 1
    Affected if The version is 6.5.0 through 6.5.24 (any 6.5.x version below 6.5.25.0)
  3. Verify the 2026.x release number
    If running a 2026.x release, confirm the specific minor version from the version information endpoint
    Affected if The version is 2026.04 or any earlier 2026.x release (before 2026.5.0)
  4. Confirm user-facing AEM access
    Verify that the AEM instance is accessible to end users or authors who could potentially click malicious links
    Affected if The instance serves content to users via web browsers, as this is a client-side XSS requiring victim interaction

You are affected if your AEM version falls below 6.5.25.0 on the 6.5.x line, or below 2026.5.0 on the 2026.x line, and users can access the instance via a browser.

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

Apply the vendor patch for CVE-2026-47935 to the affected AEM installation. Until patched, restrict user access to untrusted external sites and implement Content Security Policy (CSP) headers to mitigate XSS execution.

Recommended fix High confidence

6.5.25.0 or later (LTS track); 2026.5.0 or later (2026 track)

  1. 1. Identify the current Adobe Experience Manager version by checking the product console or version information.
  2. 2. If running 6.5.x version before 6.5.25.0, plan an upgrade to version 6.5.25.0 or later.
  3. 3. If running 2026.x version before 2026.5.0, plan an upgrade to version 2026.5.0 or later.
  4. 4. Before upgrading, review Adobe's upgrade documentation and perform a backup of the current environment.
  5. 5. Test the upgrade in a staging environment before deploying to production.
  6. 6. Apply the upgrade following Adobe's standard upgrade procedures.
  7. 7. After upgrade, verify the XSS vulnerability is resolved and the system functions correctly.
Caveat Standard AEM upgrade considerations apply - review compatibility, test custom code, and verify third-party 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
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
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,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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