CVE-2025-64804
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 confidenceAdobe Experience Manager versions 6.5.23 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privileged attacker can inject malicious JavaScript into vulnerable form inputs, which persists in the system and executes in victims' browsers when they view the affected page.
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 Adobe Experience Manager versionAccess the AEM Web Console or check the system properties file (crx-quickstart/package.properties) to identify the installed AEM version. Common paths: /system/console/system or look for version info in the AEM About screen.Affected if The installed version is 6.5.23 or earlier, or any version below 2025.12.0, or matches version 6.5 without the 6.5.24.0+ patch.
-
Identify custom form componentsReview the AEM content structure under /apps and /content for custom form components (fields with input elements). Use CRXDE Lite or the Repository Explorer to examine form field definitions in component .xml or .html files.Affected if Custom form components exist that accept user input without proper output encoding or input validation configured.
-
Audit form field input validation settingsExamine the form field component configurations in AEM Foundation Form components or custom form models. Check the Edit dialog properties of each form field component for validation settings.Affected if Form fields have no input validation (regexp pattern, required field rules) or allow raw HTML/script tags in field constraints.
-
Check for persisted script content in form dataQuery the AEM repository (using CRXDE Lite or a JCR query) for form submission data stored under /content/forms or custom form data repositories. Search for script tags, javascript: protocols, or event handler attributes.Affected if Stored form data contains unencoded script tags, onclick/onerror attributes, or javascript: URIs that indicate prior exploitation.
-
Verify low-privileged user permissions on formsIn AEM Tools > Security > Permissions, check if standard users (contributors, members of groups other than administrators) have permission to submit or create form content in the affected form paths.Affected if Low-privileged (non-admin) users have create/modify permissions on form submission nodes, allowing them to inject malicious content.
Your AEM instance is affected if the installed version is below 6.5.24.0 or 2025.12.0 AND custom or foundation form fields exist that accept user input without server-side output encoding or input validation enabled.
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 this vulnerability to upgrade to a version beyond 6.5.23. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure.
6.5.24.0 or 2025.12.0
- Download Adobe Experience Manager version 6.5.24.0 or later from the official Adobe distribution portal
- Schedule a maintenance window and back up your current AEM instance
- Stop the AEM instance before applying the upgrade
- Install AEM 6.5.24.0 or newer using the standard upgrade procedure
- After installation, verify the form fields that were previously vulnerable to ensure the XSS vulnerability is remediated
- Restart the AEM instance and confirm all services are running properly
- Test the application to ensure normal functionality is maintained after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64804 — 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-64804 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