dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64888

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 · high confidence

Adobe Experience Manager versions 6.5.23 and earlier are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability that allows a low-privileged attacker to inject malicious scripts through crafted URLs or manipulated web pages, which then execute in the victim's browser context.

MitigationUpdate Adobe Experience Manager to version 6.5.24 or later to patch the DOM-based XSS vulnerability, and implement Content Security Policy headers as defense-in-depth.

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 Adobe Experience Manager version
    Access the AEM Welcome page and locate the version information typically displayed in the bottom-left corner, or access /system/console/about to view the product version details
    Affected if The version is 6.5.23 or earlier, or falls within the range < 6.5.24.0 or < 2025.12.0, or equals 6.5 (including unpatched 6.5.x releases)
  2. Confirm AEM edition and build
    Check the specific AEM edition (like AEM Forms, AEM Sites, etc.) and verify the exact build number through the /system/console/productinfo endpoint
    Affected if The build version is below 6.5.24.0 for the 6.5.x line or below 2025.12.0 for the cloud-inspired release line
  3. Determine if untrusted user content can be submitted
    Review whether low-privilege users or unauthenticated users have the ability to submit or publish content, comments, or form inputs within AEM
    Affected if Low-privilege or unauthenticated users can inject content into pages that are rendered to other users, creating the condition for DOM-based XSS execution
  4. Assess exposure of vulnerable rendering paths
    Identify if AEM is configured to render user-supplied content through content fragments, experience fragments, or editorial components without proper sanitization
    Affected if The system allows rendering of untrusted content in contexts where DOM-based script injection can occur via crafted URLs or manipulated web pages

You are affected if your installed Adobe Experience Manager version is 6.5.23 or earlier, 6.5.x below 6.5.24.0, or any version below 2025.12.0, and low-privilege users can inject content that gets rendered to other users.

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 version 6.5.24 or later to patch the DOM-based XSS vulnerability, and implement Content Security Policy headers as defense-in-depth.

Recommended fix High confidence

AEM 6.5.24.0 (on-premise) or 2025.12.0 (AEM as a Cloud Service)

  1. Identify the current Adobe Experience Manager version in use (check /system/console/bundles or About Adobe Experience Manager page)
  2. If using AEM 6.5 on-premise: Plan upgrade to version 6.5.24.0 or later
  3. If using AEM as a Cloud Service: Verify current version and ensure upgrade to 2025.12.0 or later
  4. Back up the current AEM instance including repository, database, and configurations
  5. Review Adobe's official AEM 6.5.24 upgrade documentation and release notes for any specific requirements
  6. Execute the upgrade following Adobe's recommended upgrade procedures
  7. After upgrade, verify the AEM instance is running correctly and all bundles are active
  8. Validate that the DOM-based XSS vulnerability is no longer present by testing the previously vulnerable endpoint
Caveat Review Adobe 6.5.24 release notes for any compatibility or configuration changes before upgrading

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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