CVE-2025-64790
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 · moderate confidenceAdobe Experience Manager versions 6.5.23 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability. A low-privilege attacker can inject malicious JavaScript into form fields, which persists in the system. When other users view pages containing these compromised fields, the malicious script executes in their browsers, potentially enabling session hijacking, credential theft, or further network propagation.
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 the installed AEM versionAccess the AEM system information page (typically at /system/console/bundles or /crx/packmgr/service.jsp) or run the version check command from the AEM SDK. Look for the exact version number in the AEM About page (Help > About Adobe Experience Manager).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.
-
Identify form fields that accept user inputReview all AEM forms and user-generated content areas. Use AEM's content finder or query the repository (via CRXDE or the Query Builder) for nodes containing form components such as text fields, textareas, or rich text editors.Affected if Forms accept user input and store it in the repository without proper sanitization.
-
Search for stored XSS payloads in contentQuery the AEM content repository (via CRXDE Lite, Query Builder, or Groovy script) for common XSS patterns in form-stored content. Look for script tags, javascript: URLs, event handlers (onerror, onload), or encoded variants in text fields.Affected if Any form field content contains script tags, javascript: protocols, or HTML event attributes that were not explicitly authored.
-
Review recent form submissions for suspicious contentCheck the AEM audit log (accessible via the Operations dashboard or crx-quickstart/logs) for form submission activities. Look for entries containing XSS-relevant characters and patterns.Affected if Recent form submissions contain unusual script-related characters or patterns that suggest injection attempts.
-
Inspect Content-Security-Policy headersUse browser developer tools or a curl command to inspect the HTTP response headers from AEM pages. Look for the Content-Security-Policy header and evaluate whether it restricts inline scripts and external script sources.Affected if CSP headers are missing or configured to allow inline scripts, which would enable XSS execution.
You are affected if your AEM version is 6.5.x below 6.5.24.0 or any version below 2025.12.0, AND your forms store user input without sanitization, AND malicious scripts have been injected into form fields that execute when viewed by other users.
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 to AEM 6.5.24 or later. Additionally, implement input validation and output encoding on all form fields, and configure Content-Security-Policy headers to mitigate XSS execution.
AEM 6.5.24.0 or later (or AEM as a Cloud Service 2025.12.0 if using the cloud offering)
- 1. Backup your current AEM instance and database before starting the upgrade process
- 2. Review the Adobe Experience Manager 6.5.24.0 release notes for any migration requirements or breaking changes
- 3. Ensure your system meets the prerequisites for upgrading to AEM 6.5.24.0 or later
- 4. Use the AEM Upgrade Planner to assess compatibility and identify potential issues
- 5. Perform a staging/test upgrade in a non-production environment first
- 6. Upgrade your production environment to AEM 6.5.24.0 (or 2025.12.0 if using that release line)
- 7. After upgrade, verify that custom code and integrations still function correctly
- 8. Test the fix by attempting to inject malicious scripts into form fields to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64790 — 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-64790 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