CVE-2025-64820
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 versions 6.5.23 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. The malicious payload is stored 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.
-
Identify installed AEM versionAccess the AEM System Information console at /system/console/status-productinfo or check the version.properties file in the crx-quickstart folder. Alternatively, go to AEM Welcome > Information > Version.Affected if The installed version is 6.5.23 or earlier, or any 6.5.x version below 6.5.24.0, or any version below 2025.12.0.
-
Confirm AEM edition and baselineCheck if the instance is running the 6.5 LTS baseline by reviewing the product name in /system/console/status-productinfo or the AEM About page (Help > About Adobe Experience Manager).Affected if The instance is on the 6.5 LTS baseline (any patch level) or the 2025.12.0 baseline.
-
Identify form components in useReview the AEM Forms implementation by checking /libs/fd/fm/components or custom form component paths in /apps. Look for Adaptive Form, Core Form, or Foundation Form components used in content pages.Affected if The environment uses AEM Forms components (Adaptive Forms, Core Components forms, or Foundation forms) to collect user input on published pages.
-
Check for unvalidated form field configurationsExamine the form field component configurations in the CRX/DE repository (crx/de) under /apps or /libs where form components are defined. Look for input type definitions and whether they reference XSS protection or input validation rules.Affected if Form field components lack XSS protection rules or input validation configuration, allowing raw HTML/script injection into stored form data.
-
Verify stored form data handlingCheck the data storage location for forms (typically under /content/forms/af or custom form submission endpoints) to confirm form submissions are stored without server-side sanitization.Affected if Form submissions are stored directly in the repository or database without encoding or sanitization before storage.
The environment is affected if running AEM 6.5.23 or earlier (6.5.x), or any version before 2025.12.0, and the instance uses AEM Forms or form components that accept and store user-submitted content without input validation.
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 official patch. Additionally, implement input validation and output encoding on form fields, and configure Content Security Policy (CSP) headers to mitigate XSS execution.
AEM 6.5.24.0 or later, or AEM 2025.12.0 or later
- 1. Identify current Adobe Experience Manager version by navigating to /system/console/configMgr or checking the About Adobe Experience Manager page
- 2. Review the upgrade documentation at helpx.adobe.com for detailed migration steps
- 3. Create a full backup of the current AEM instance including repository, database, and configurations
- 4. Schedule a maintenance window for the upgrade process
- 5. Upgrade Adobe Experience Manager to version 6.5.24.0 or later (for the 6.5.x release line)
- 6. Alternatively, if using the newer release cadence, upgrade to version 2025.12.0 or later
- 7. After upgrade, verify that the vulnerable form fields properly sanitize user input
- 8. Test the application thoroughly, especially form submission and rendering functionality
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-64820 — 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-64820 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