dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64569

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

Adobe Experience Manager versions 6.5.23 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability. Attackers can inject malicious scripts that execute in the victim's browser context through manipulated URLs or web pages, leveraging the DOM manipulation to reflect crafted input.

MitigationUpdate Adobe Experience Manager to a version newer than 6.5.23 once the vendor patch is released. Additionally, implement Content Security Policy (CSP) headers and input validation sanitization on affected endpoints.

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 installed AEM version
    Access the AEM About page (typically at /libs/granite/ui/content/shell/about.html or through the Help menu > About Adobe Experience Manager), or check the version displayed in the AEM Welcome page footer. Alternatively, review version information in AEM logs or the system console (/system/console).
    Affected if The installed version is 6.5.23 or earlier, or any 6.5.x version below 6.5.24.0, or any version below 2025.12.0.
  2. Confirm the AEM edition and release track
    Verify whether the installation is the 6.5 LTS (Long Term Support) release or the quarterly release track. Check the version string format - LTS versions appear as 6.5.x while quarterly releases appear as year.month (e.g., 2025.12).
    Affected if The installation is on the 6.5 LTS track at version 6.5.23 or below, or on any quarterly release before 2025.12.0.
  3. Determine if user-generated content or URL parameters are processed client-side
    Review AEM components or custom code that handle URL parameters, form inputs, or content from external sources. Inspect any client-side JavaScript that reads window.location, document.URL, or URL parameters and renders output to the page DOM.
    Affected if The environment uses custom components or third-party integrations that process and reflect user input into the DOM without server-side sanitization or CSP protection.
  4. Check for Content Security Policy (CSP) headers
    Inspect HTTP response headers on AEM-published pages. Look for CSP header configuration in the Apache HTTP Server (httpd.conf), AEM Dispatcher configuration, or AEM policies. Verify if 'script-src' directives are restrictive.
    Affected if No CSP headers are configured, or CSP headers allow 'unsafe-inline' or overly permissive source whitelists that would not mitigate DOM-based XSS.

A user is affected if their AEM installation version is 6.5.23 or earlier, or any version below 6.5.24.0 (LTS) or 2025.12.0 (quarterly), and the environment processes user input in client-side code without 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.24.0 / 2025.12.0 or later
Fixed in 6.5.24.02025.12.0
Interim mitigation

Update Adobe Experience Manager to a version newer than 6.5.23 once the vendor patch is released. Additionally, implement Content Security Policy (CSP) headers and input validation sanitization on affected endpoints.

Recommended fix High confidence

6.5.24.0 (or later for 6.5.x line); 2025.12.0 (or later for newer releases)

  1. Upgrade Adobe Experience Manager to version 6.5.24.0 or later for the 6.5.x release line
  2. Alternatively, upgrade to version 2025.12.0 or later if using the newer release cadence
  3. After upgrading, verify the XSS vulnerability is no longer present by reviewing the security patch notes
  4. Test the upgrade in a non-production environment before deploying to production
Caveat Standard AEM upgrade considerations apply - test custom code and integrations in staging before production deployment

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 / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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