CVE-2025-64591
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 in form fields. A low-privileged authenticated attacker can inject malicious JavaScript into these fields, which persists in the system. When other users view pages containing the compromised form fields, the malicious script executes in their browsers, potentially allowing session hijacking or credential theft.
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.
-
Determine AEM product versionAccess the AEM Web Console Bundle information page at /system/console/bundles or check the Product Version via the AEM Welcome page > Tools > Operations > Diagnosis > Version Info. Compare the displayed version against the affected ranges: versions before 6.5.24.0, version 6.5, or builds earlier than 2025.12.0.Affected if The installed version is 6.5.x where x is 23 or lower, equals 6.5 exactly, or is any 2025 build earlier than the December 2025 release.
-
Verify AEM Forms module is enabledNavigate to /system/console/bundles and search for bundles containing 'Forms' in the name, or access AEM Forms at /aem/forms (if available). Confirm whether the Forms framework is installed and active on the instance.Affected if AEM Forms is installed and running on the system, as the XSS vulnerability exists specifically within form field components.
-
Identify low-privileged user access to form editingCheck the group and permission configuration at /useradmin or CRXDE Lite (/crx/de). Verify if users assigned to 'forms-user', 'contributors', or custom low-privilege groups have Create or Modify permissions on content paths under /content or /etc that contain form structures.Affected if Low-privileged users (non-admin) have write permissions on form-related content nodes, as the CVE requires a low-privileged authenticated attacker to inject the malicious script.
-
Inspect form field content for suspicious payloadsUse CRXDE Lite (/crx/de) or the Query tool to search form field content nodes under /content/forms and /etc/designs for common XSS patterns such as <script>, javascript:, onerror=, onload=, or encoded variants. Alternatively, export form data via the Forms Manager and scan for HTML/script tags in field values.Affected if Any form fields contain unsanitized HTML or script tags that could execute JavaScript when other users view the rendered form.
Your environment is affected if you are running AEM versions below 6.5.24.0 (or pre-December 2025), the AEM Forms module is enabled, and low-privileged users have edit access to form content.
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 Adobe Experience Manager version 6.5.24 or later. Until patched, implement output encoding and input validation on affected form fields, and consider restricting low-privileged user permissions to form creation/editing capabilities.
Adobe Experience Manager 6.5.24.0 or later (or 2025.12.0 and later for cloud)
- Ensure you have a complete backup of your AEM instance and author/publish environments
- Review the Adobe Experience Manager 6.5.24 release notes for any migration or configuration changes required
- Test the upgrade in a non-production environment first
- Stop the AEM instance(s)
- Install Adobe Experience Manager 6.5.24.0 or later on author instance, following standard upgrade procedures
- Verify all custom code, configurations, and integrations work correctly
- Replicate the changes to publish instances following your deployment process
- Clear browser cache and test that the vulnerable form fields no longer allow XSS injection
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64591 — 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-64591 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