dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64551

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 (XSS) vulnerability in Adobe Experience Manager versions 6.5.23 and earlier allows low-privileged attackers to inject malicious scripts into victims' browsers via crafted URLs or manipulated web pages, exploiting improper handling of DOM elements in the web application.

MitigationUpgrade Adobe Experience Manager to version 6.5.24 or later to patch the vulnerability, and implement Content Security Policy (CSP) headers as a defense-in-depth measure against 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. Determine Adobe Experience Manager version
    Access the AEM Welcome page or check the product version via the system information console (typically at /system/console/systeminfo or /libs/granite/ui/content/shell/about.html)
    Affected if Installed version is 6.5.x (any build before 6.5.24.0) or falls below version 2025.12.0 (e.g., 2024.x, 2025.x versions before the December 2025 release)
  2. Identify active AEM instance type
    Verify whether the AEM instance is running as an author environment, publish environment, or both by checking the run modes via the OSGi web console at /system/console/vmstat
    Affected if The instance is accessible to low-privileged users (such as anonymous users on publish instances or standard users on author instances) who can craft URLs or manipulate web page inputs
  3. Inspect DOM handling in custom components
    Review any custom HTL, JavaScript, or JSP components that process URL parameters, form inputs, or client-side data by examining scripts under /apps and checking for direct DOM manipulation without sanitization
    Affected if Custom components accept user-controlled input and directly inject it into the DOM without using AEM's built-in XSS protection or context-aware encoding
  4. Check for Content Security Policy headers
    Inspect HTTP response headers from the AEM server using browser developer tools or a command-line tool (e.g., curl -I <aem-url>) to see if CSP headers are present
    Affected if CSP headers are absent or minimally configured, providing no defense-in-depth layer against DOM-based XSS exploitation

The environment is affected if the installed AEM version is 6.5.x before 6.5.24.0 or any version below 2025.12.0, especially when the instance accepts input from low-privileged users without CSP protections in place.

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

Upgrade Adobe Experience Manager to version 6.5.24 or later to patch the vulnerability, and implement Content Security Policy (CSP) headers as a defense-in-depth measure against XSS attacks.

Recommended fix High confidence

AEM 6.5.24.0 or later (6.5.x line) / 2025.12.0 or later (2025 release track)

  1. Identify current Adobe Experience Manager version in use
  2. Navigate to Adobe Security Notifications page (helpx.adobe.com) for CVE-2025-64551 to obtain the official security bulletin
  3. Download and plan upgrade to AEM 6.5.24.0 or later for 6.5.x installations, or to 2025.12.0 or later for newer release tracks
  4. Test the upgrade in a non-production environment before deploying to production
  5. Schedule maintenance window and backup current AEM instance
  6. Perform the upgrade following Adobe's official documentation
  7. Verify the XSS vulnerability is resolved by testing with the crafted URL vector mentioned in the security bulletin
  8. Deploy to production environment
Caveat Point releases like 6.5.24 are typically backward-compatible; however, review Adobe's 6.5.24 release notes for any exceptions 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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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