CVE-2025-64575
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 stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager affecting versions 6.5.23 and earlier. A low-privileged attacker can inject malicious JavaScript into form fields, which persists in the system and executes in victim browsers when they view pages containing the compromised fields.
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.
-
Check installed AEM versionAccess the AEM Web Console (go to /system/console/config) or check the version from the AEM Welcome page. Navigate to Help > Version to view the exact version number.Affected if The installed version is 6.5.23 or earlier, 2025.12.0 or earlier, or exactly 6.5.x without the 6.5.24.0 patch.
-
Identify form components in useReview the AEM content structure under /content for Adaptive Forms, Form Fragments, or custom form components. Check the AEM Forms UI at /aem/forms.html to list all published forms.Affected if Forms or form fragments exist in the system, as the XSS payload would be injected into form fields.
-
Verify low-privileged user access to formsCheck user/group permissions in AEM User Management (go to /security/users.html or /security/groups.html). Identify if standard users or custom groups have access to author or edit form content.Affected if Low-privileged users (non-admin) have create, modify, or contributor permissions on form content paths.
-
Inspect stored form field data for XSS patternsQuery the repository under /content/forms or /content/dam/forms for any stored field values. Use CRXDE Lite (go to /crx/de) or the Query tool to search for common XSS patterns like <script, javascript:, onerror=, or other HTML/script tags in form field values.Affected if Form data stored in the repository contains unsanitized HTML or script tags that could execute in victim browsers.
You are affected if your AEM version is below 6.5.24.0 (or below 2025.12.0) AND your system contains forms with user-editable fields accessible to low-privileged accounts.
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
Update Adobe Experience Manager to version 6.5.24 or later to obtain the security patch. Additionally, implement input validation and output encoding on form fields as a defense-in-depth measure.
Adobe Experience Manager 6.5.24.0 (or 2025.12.0 for newer release trains)
- Upgrade Adobe Experience Manager to version 6.5.24.0 or later for the 6.5.x release train
- If using the newer release train (2024.x), upgrade to 2025.12.0 or later
- After upgrade, verify the form fields mentioned in the vulnerability are no longer susceptible to stored XSS
- Test the fix in a staging environment before deploying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64575 — 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-64575 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