CVE-2025-64543
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 · moderate confidenceAdobe Experience Manager versions 6.5.23 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability where malicious scripts can be executed in a victim's browser via crafted URLs or manipulated web pages. This is a client-side vulnerability where JavaScript reads input from the DOM (likely URL parameters) and reflects it back without proper sanitization, allowing script execution in the context of the user's session.
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 Adobe Experience Manager installationLocate the AEM instance and access the product information page. On AEM, this is typically found at /system/console or by checking the version.properties file in the crx-quickstart directory. Alternatively, access the AEM Welcome page and navigate to Help > About Adobe Experience Manager.Affected if The installation is confirmed to be Adobe Experience Manager
-
Determine installed AEM versionCheck the AEM version by accessing the OSGi web console at /system/console/bundles or by running the AEM version check command appropriate to your deployment. For AEM as a Cloud Service, check via Cloud Manager or the developer console.Affected if The installed version is 6.5.23 or earlier, or any 6.5.x version below 6.5.24.0, or version 2025.12.0 or below on AEM as a Cloud Service
-
Confirm version falls within affected rangesCompare your identified version number against the affected ranges: versions less than 6.5.24.0, versions less than 2025.12.0, or exactly version 6.5. Document the full version string including any service packs or cumulative fix packs installed.Affected if The version is less than 6.5.24.0, less than 2025.12.0, or exactly equals 6.5 (without a higher service pack)
-
Review custom or third-party components using URL parametersAudit any custom AEM components, templates, or third-party integrations that read URL parameters or DOM input client-side. Search for JavaScript code using location.search, URLSearchParams, or document.referrer that reflects values back into the HTML without proper encoding.Affected if Custom components exist that accept and reflect URL parameters client-side without output encoding
You are affected if your AEM installation version is 6.5.23 or earlier, 6.5.x below 6.5.24.0, or any version below 2025.12.0 on AEM as a Cloud Service.
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 a version newer than 6.5.23 once available, and implement input validation and output encoding on affected endpoints. Consider deploying Content Security Policy (CSP) headers as a defense-in-depth measure.
AEM 6.5.24.0 (for 6.5.x line) or 2025.12.0 (for cloud releases)
- 1. Identify the current Adobe Experience Manager version in use (check /system/console/bundles or About Adobe Experience Manager page)
- 2. If running 6.5.x line (6.5.23 or earlier), upgrade to AEM 6.5.24.0 or later
- 3. If running 2025.x cloud release (2025.11 or earlier), upgrade to 2025.12.0 or later
- 4. After upgrade, verify the AEM instance starts successfully and all bundles are in active state
- 5. Test critical workflows to ensure functionality is intact
- 6. Clear browser cache before testing to ensure new version assets are loaded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64543 — 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-64543 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