CVE-2025-64794
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 where low-privileged attackers can inject malicious JavaScript into form fields. The injected payload persists on the server and executes in victims' browsers when they navigate to pages containing the compromised form 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 Adobe Experience Manager System Information page at /system/console/status-productinfo or check the version.properties file in the crx-quickstart directoryAffected if The version is 6.5.x where x <= 23, or the version shows 2025.x where x <= 12, or the version is listed simply as 6.5 without a point release number indicating it is earlier than 6.5.24.0
-
Verify Forms module is in useCheck if AEM Forms add-on or Adaptive Forms feature is installed by navigating to /libs/fd/fm/fc/widgets source or by reviewing installed packages in the Package Manager at /crx/packmgrAffected if AEM Forms or Adaptive Forms modules are installed and enabled on the instance
-
Check for low-privileged user access to form editingReview user permissions in AEM Groups and Permissions at /useradmin to identify if standard users or contributors have create or modify permissions on form content paths under /content/formsAffected if Users with low-privilege (contributor, member, or non-admin groups) have write access to form definitions or form data storage paths
-
Inspect form field content for injected scriptsNavigate to the Forms Manager at /aem/forms or query the repository under /content/forms for any stored XSS payloads. Inspect form field XML or JSON definitions for suspicious script tags, javascript: handlers, or encoded payloads in label, placeholder, or default value fieldsAffected if Any form fields contain script tags, event handlers, or malicious JavaScript payloads that were not authored by administrators
The environment is affected if AEM version is earlier than 6.5.24.0 or earlier than 2025.12.0 AND the instance has Forms functionality enabled with accessible form fields that low-privileged users can modify.
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 later than 6.5.23 when the patch becomes available, or implement output encoding and input validation on affected form fields as a compensating control.
AEM 6.5.24.0 or later for on-premise 6.5.x; AEM 2025.12.0 or later for Cloud Service/2025 releases
- 1. Identify the current Adobe Experience Manager version in use (check /system/console/bundles or the About AEM page)
- 2. For AEM 6.5.x on-premise installations: Plan upgrade to version 6.5.24.0 or later
- 3. For AEM as a Cloud Service or 2025 releases: Plan upgrade to version 2025.12.0 or later
- 4. Review the Adobe release notes for the target version to understand changes and ensure compatibility
- 5. Create a staging/test environment with the current production configuration
- 6. Apply the upgrade in the test environment and validate all custom components, integrations, and workflows
- 7. Perform thorough testing of form handling and user-generated content to confirm the XSS fix works correctly
- 8. After successful testing, schedule a maintenance window and apply the upgrade to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64794 — 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-64794 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