dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64564

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-10
Fix available
A fix is available. Upgrade to 6.5.24.0 / 2025.12.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.23 and earlier are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability that could be exploited by a low privileged attacker to execute malicious scripts in the context of the victim's browser. Exploitation of this issue requires user interaction, such as visiting a crafted URL or interacting with a manipulated 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 · moderate confidence

DOM-based Cross-Site Scripting vulnerability in Adobe Experience Manager versions 6.5.23 and earlier allows low-privileged attackers to execute malicious scripts in victims' browsers through crafted URLs or manipulated web pages, with exploitation requiring user interaction.

MitigationApply the vendor patch for Adobe Experience Manager to a version newer than 6.5.23; for environments where immediate patching is not feasible, implement Content Security Policy (CSP) headers and sanitize user-supplied input in affected DOM operations.

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< 2025.12.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 Adobe Experience Manager version
    Access the AEM System Information console at /system/console/status-productinfo or check the version.properties file in the crx-quickstart folder on the server filesystem
    Affected if The version displayed is 6.5.x (any patch level), or < 6.5.24.0, or < 2025.12.0 (for newer release trains)
  2. Confirm AEM release train
    Locate the full version string in the AEM Web Console under Product Information, or query the Sling getProperty endpoint at /system/console/products.json to retrieve the detailed version metadata
    Affected if The release train shows 6.5 without reaching 6.5.24.0, or the year-based release is below 2025.12.0
  3. Determine if affected DOM operations are in use
    Review AEM component usage in the repository (via CRXDE Lite at /crx/de or package manager) for custom components that handle DOM manipulation without sanitization, particularly in Sightly/HTL templates or client-side JavaScript handling URL parameters or user inputs
    Affected if Custom AEM components or client-side scripts process unsanitized input from request parameters, URL paths, or user-controlled data within DOM operations
  4. Assess user-facing attack surface
    Check if the AEM Publish instance is accessible externally, as DOM-based XSS typically requires victims to access crafted URLs or manipulated pages; inspect dispatcher configurations and publish instance accessibility
    Affected if The publish instance or author preview functionality is accessible to low-privileged external users who could be tricked into clicking malicious links

You are affected if your installed AEM version is 6.5.x, < 6.5.24.0, or < 2025.12.0, AND your AEM deployment exposes DOM manipulation functionality that handles unsanitized user input accessible to low-privilege attackers.

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.24.0 / 2025.12.0 or later
Fixed in 6.5.24.02025.12.0
Interim mitigation

Apply the vendor patch for Adobe Experience Manager to a version newer than 6.5.23; for environments where immediate patching is not feasible, implement Content Security Policy (CSP) headers and sanitize user-supplied input in affected DOM operations.

Recommended fix High confidence

6.5.24.0 (for 6.5.x line) or 2025.12.0+ (for newer release train)

  1. Identify the current Adobe Experience Manager version (check /system/console or version.xml)
  2. Determine which release train the instance belongs to (6.5.x legacy or 2025.x newer releases)
  3. Schedule a maintenance window for the upgrade
  4. Perform a full backup of the AEM instance including repository and database
  5. Review Adobe's official upgrade documentation for the target version
  6. Test the upgrade in a non-production environment first
  7. Apply the upgrade to production environment: upgrade to 6.5.24.0 or later for 6.5.x line, or 2025.12.0 or later for newer release train
  8. Verify the XSS vulnerability is resolved by testing the fix
Caveat Standard AEM upgrade considerations apply: review custom code compatibility, test third-party integrations, and verify content structure changes

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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