CVE-2025-64537
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 lead to arbitrary code execution. An attacker could exploit this vulnerability by injecting malicious scripts into a web page that are executed in the context of the victim's browser. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality and integrity impact as high. Exploitation of this issue requires user interaction in that a victim must visit a crafted malicious 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 confidenceAdobe Experience Manager versions 6.5.23 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability that allows attackers to inject malicious scripts into web pages. When victims visit these crafted pages, the malicious JavaScript executes in their browsers, enabling session takeover and arbitrary code execution.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/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.
-
Check AEM version against affected rangesAccess the AEM Web Console (system/console/systeminfo) or check the crx-quickstart folder for the version.properties file. Look for the Product Version or build number.Affected if The installed version is < 6.5.24.0, or < 2025.12.0, or exactly 6.5 (any 6.5.x version below 6.5.24.0)
-
Identify AEM as the deployed productConfirm that Adobe Experience Manager is running in your environment by checking the application's login page, console, or running processes for 'aem' or 'Adobe Experience Manager' identifiers.Affected if AEM is confirmed as the deployed product and version falls within affected ranges
-
Review custom AEM components for potential DOM XSS patternsExamine any custom OSGi bundles, Sightly/JSP components, or client-side JavaScript in /apps for improper handling of user input in DOM manipulation methods such as innerHTML, eval(), or document.write(). Search for patterns like += with unescaped variables in script contexts.Affected if Custom components exist and contain unsafe DOM manipulation without proper input sanitization
-
Check for exposed UI components accessible to unauthenticated usersReview the Dispatcher or AEM publish tier configurations to identify which endpoints and selectors are publicly accessible. Check for unauthenticated access to components that render user-supplied content.Affected if Publicly accessible pages render user-controlled content without proper encoding
Your environment is affected if you are running any Adobe Experience Manager version below 6.5.24.0 or below 2025.12.0 that has custom components or exposed UI rendering untrusted input without sanitization.
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
Apply the Adobe security patch for AEM 6.5.23 or later, and review custom AEM components for improper DOM manipulation that could be exploited.
6.5.24.0 (or 2025.12.0 for newer release line)
- Upgrade Adobe Experience Manager to version 6.5.24.0 or later for the 6.5.x release line
- Alternatively, upgrade to version 2025.12.0 or later for the newer release line
- After upgrading, verify that the XSS vulnerability is remediated by testing with the identified attack vectors
- Ensure all custom code and third-party integrations are tested post-upgrade for compatibility
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64537 — 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-64537 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