dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64545

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 vulnerability in Adobe Experience Manager versions 6.5.23 and earlier allows low-privileged attackers to inject malicious JavaScript into victim's browser through crafted URLs or manipulated web pages.

MitigationApply Adobe security patch (AEM 6.5.24 or later). Until patched, implement strict Content Security Policy headers and validate all user-supplied input 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 AEM version via system console
    Access the AEM system console at /system/console/productinfo and locate the 'Version' field, or check the version.properties file in the crx-quickstart folder
    Affected if The displayed version number is lower than 6.5.24.0 or lower than 2025.12.0 (for cloud/2025 releases)
  2. Check AEM package version via CRXDE or Package Manager
    Open CRXDE Lite at /crx/de or access Package Manager at /pkgmgr and review the Adobe Experience Manager core bundle version
    Affected if The installed AEM bundle version corresponds to a release before 6.5.24.0 or before the 2025.12.0 release
  3. Verify Content Security Policy configuration
    Inspect the Apache Sling servlet filter or dispatcher configuration for 'Content-Security-Policy' headers. Check the org.apache.sling.security.impl.ReferrerFilter OSGi configuration at /system/console/configMgr
    Affected if No CSP headers are defined or the CSP allows 'unsafe-inline' scripts, increasing exploitability of any XSS flaw
  4. Review affected endpoints for user input reflection
    Analyze custom AEM components, sightly templates, or any custom servlets that accept URL parameters and reflect them into the HTML output without proper encoding
    Affected if Applications contain endpoints or components that reflect URL parameters directly into DOM output without contextual encoding

A user is affected if their installed AEM version is below 6.5.24.0 (for 6.x releases) or below 2025.12.0 (for cloud releases) AND the application reflects user input into the browser without proper encoding.

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 Adobe security patch (AEM 6.5.24 or later). Until patched, implement strict Content Security Policy headers and validate all user-supplied input on affected endpoints.

Recommended fix High confidence

6.5.24.0 (for AEM 6.5.x line)

  1. Identify the current Adobe Experience Manager version by checking the AEM product information in the Welcome page or system console
  2. Confirm the installed version is affected: any version < 6.5.24.0 or < 2025.12.0
  3. Create a complete backup of the AEM instance including the repository, database, and configuration files
  4. Test the upgrade in a non-production environment to verify compatibility with existing customizations
  5. Download Adobe Experience Manager 6.5.24.0 from the official Adobe distribution portal (Software Distribution)
  6. Follow Adobe's official AEM 6.5 Upgrade documentation to perform the upgrade
  7. After upgrading, verify the version number matches 6.5.24.0 and validate that the XSS vulnerability is resolved
Caveat Review the AEM 6.5.24.0 release notes for any breaking changes, deprecated features, or compatibility considerations with existing custom code and integrations

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