dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64887

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

DOM-based Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.23 and earlier allows low-privileged attackers to execute malicious JavaScript in victim's browser through manipulation of the DOM. Exploitation requires user interaction such as clicking a crafted URL or interacting with a manipulated web page.

MitigationApply available vendor patches for Adobe Experience Manager. Additionally, implement Content Security Policy (CSP) headers and input validation/sanitization on affected endpoints to mitigate XSS attacks.

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 Welcome page or system console (e.g., /crx/packmgr/service.jsp) and locate the version number displayed in the AEM product information or version manifest
    Affected if The displayed version is < 6.5.24.0, < 2025.12.0, or exactly 6.5
  2. Verify AEM 6.5 service pack level
    In the AEM System Console (located at /system/console/configMgr), check the com.day.cq.commons.impl.VersionInfoImpl configuration or the About Adobe Experience Manager page for the specific service pack version
    Affected if The service pack is anything less than 6.5.24.0 (for example, 6.5.0 through 6.5.23)
  3. Confirm AEM as a Cloud Service version
    Check the Cloud Manager environment details or the AEM version shown in the Developer Console for AEM as a Cloud Service deployments
    Affected if The version is earlier than 2025.12.0 (for example, any 2024.x or early 2025 release)
  4. Assess user-facing input handling
    Review any custom AEM components, dialogs, or forms that accept user input and render content back into the page DOM without server-side sanitization
    Affected if Custom components manipulate the DOM with unsanitized user-supplied data and are accessible to low-privileged users

Your environment is affected if the installed AEM version falls below 6.5.24.0 for on-premise 6.5 installations, below 2025.12.0 for AEM as a Cloud Service, or exactly equals 6.5 without a service pack applied.

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 available vendor patches for Adobe Experience Manager. Additionally, implement Content Security Policy (CSP) headers and input validation/sanitization on affected endpoints to mitigate XSS attacks.

Recommended fix High confidence

Adobe Experience Manager 6.5.24.0 (or later 6.5.x release)

  1. 1. Backup your current Adobe Experience Manager instance and verify all custom configurations.
  2. 2. Review the Adobe Experience Manager 6.5.24.0 release notes for any compatibility notes or known issues.
  3. 3. Download Adobe Experience Manager 6.5.24.0 or later from the official Adobe distribution portal (Adobe Software Distribution).
  4. 4. Install the new version following the standard AEM upgrade procedure: stop the AEM instance, run the upgrade installer, verify the migration, and restart the instance.
  5. 5. After upgrade, validate that all custom applications, workflows, and integrations function correctly.
  6. 6. Verify the XSS vulnerability is remediated by testing the previously vulnerable endpoint.

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-64887 — 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-64887 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