dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64562

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. This client-side vulnerability allows a low-privileged attacker to inject malicious scripts that execute in the victim's browser through DOM manipulation, typically via crafted URLs or manipulated web pages. Exploitation requires user interaction such as visiting a malicious URL.

MitigationApply the vendor patch when available and implement Content Security Policy (CSP) headers to mitigate XSS execution. Review and sanitize client-side JavaScript code that handles user input and DOM manipulation.

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 the installed AEM version
    Access the AEM About page (Help > About Adobe Experience Manager) or inspect the version.properties file in the crx-quickstart folder, or query the system console at /system/console/systeminfo
    Affected if The installed version is 6.5.23 or earlier, or falls within version range 6.5, or is earlier than 2025.12.0
  2. Verify the specific AEM 6.5.x build version
    Check the full version string in the AEM About page or version.properties (e.g., 6.5.0.x through 6.5.23.x)
    Affected if The version is 6.5.23.x or any 6.5.x version earlier than 6.5.24.0
  3. Identify if DOM-handling components are accessible
    Review the AEM web console bundles and look for components related to HTML/Content rendering, specifically those handling DOM manipulation or user-supplied markup in author or publish instances
    Affected if DOM-rendering bundles are in active state on publish-facing instances accessible to low-privilege users
  4. Check for exposed endpoints handling user input in DOM context
    Review published endpoints and servlets under /bin, /content, or /libs that accept URL parameters and return unfiltered HTML or JavaScript to the client
    Affected if Unsanitized URL parameters or form inputs are reflected in client-side responses without contextual encoding
  5. Inspect current Content Security Policy configuration
    Check the HTTP response headers (CSP X-Frame-Options or custom CSP headers) on the AEM publish instance using browser DevTools or a curl request to published pages
    Affected if CSP headers are missing, weak, or contain unsafe directives (like unsafe-inline) that would permit script execution from injected payloads

A user is affected if their AEM installation version is 6.5.23.x or earlier, or 6.5.x, or any version earlier than 2025.12.0 and the publish instance exposes DOM-handling features to low-privilege users without adequate 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

Apply the vendor patch when available and implement Content Security Policy (CSP) headers to mitigate XSS execution. Review and sanitize client-side JavaScript code that handles user input and DOM manipulation.

Recommended fix Moderate confidence

AEM 6.5.24.0 or later (6.5.x line) / AEM 2025.12.0 or later (as a Cloud Service)

  1. Backup the current AEM instance and database
  2. Review the AEM 6.5.24.0 or 2025.12.0 release notes for any migration requirements
  3. Test the upgrade in a non-production environment first
  4. Download and install AEM 6.5.24.0 (for on-premise 6.5 installations) or deploy 2025.12.0 (for AEM as a Cloud Service)
  5. Verify that the XSS vulnerability is resolved by testing the affected endpoints
  6. Deploy to production after successful validation
Caveat Review Adobe release notes; major version upgrades may require content repository migrations and dependency updates

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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