CVE-2025-64560
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 · uneditedAdobe 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 confidenceDOM-based Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.23 and earlier allows low-privilege attackers to execute malicious JavaScript in victims' browsers through crafted URLs or manipulated web pages.
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< 6.5.24.0< 2025.12.0= 6.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed AEM versionAccess the AEM System Information console (typically at /system/console/status-htmlpl) or check the version.properties file in the crx-quickstart folderAffected if The version displayed is earlier than 6.5.24.0, equal to 6.5.x, or earlier than 2025.12.0 release
-
Confirm AEM edition and release lineVerify whether the installation is AEM 6.5 (classic) or the newer 2025.x release train by checking the version string in the system consoleAffected if The version shows 6.5 without the .24 suffix or shows a 2025 release prior to the December 2025 update
-
Verify web interface exposureConfirm that the AEM web interface (author or publish instance) is accessible and handles user-supplied URLs or web contentAffected if The AEM web interface is active and can accept or render external content without sanitization
You are affected if your AEM installation version is 6.5.x (any build before 6.5.24) or falls below the 2025.12.0 release line.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.5.24.02025.12.0
Upgrade Adobe Experience Manager to version 6.5.24 or later to obtain the security patch; alternatively, apply the official Adobe security hotfix if available.
AEM 6.5.24.0 or later
- Verify current Adobe Experience Manager version by checking the AEM welcome page or system console
- Review the AEM 6.5.24.0 release notes and known issues at helpx.adobe.com before upgrading
- Create a full backup of the AEM repository (crx-quickstart) and database
- Schedule a maintenance window as upgrade requires downtime
- Stop the AEM instance before beginning upgrade
- Download AEM 6.5.24.0 or later from Adobe Software Distribution or your licensing portal
- Run the upgrade installer following Adobe's documented upgrade procedure for AEM 6.5
- After upgrade, verify the AEM instance starts successfully and all bundles are in active state
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64560 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64560 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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