CVE-2025-64580
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. A low-privileged attacker can inject malicious JavaScript into vulnerable form fields, which will execute when other users browse to 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 installed AEM versionNavigate to the AEM welcome page or access the system information console (typically at /system/console/systeminfo or via the Help menu > About Adobe Experience Manager). The version is displayed on the welcome screen or in the product info section.Affected if The displayed version number is less than 6.5.24.0 or less than 2025.12.0 (for cloud-enabled releases).
-
Verify AEM 6.5 release lineConfirm the product is the AEM 6.5 release line (not a different AEM version such as 6.4 or Cloud Service). Check the product name displayed in the About dialog or welcome page.Affected if The product is AEM version 6.5.x and the minor version is 23 or lower.
-
Identify exposed form componentsReview the AEM instance for custom or extended form components (foundation form fields, customcq components, or third-party form widgets) that accept user input and render output. Check the CQ:EditConfig or CQ:Dialog configurations for these components.Affected if The instance hosts custom form components that render user-supplied input without visible output encoding in the view template or sling:include logic.
The environment is affected if the installed AEM version is 6.5.23 or earlier, or any 6.5.x version below 6.5.24.0, and the instance exposes form fields that accept user input and render it back without proper encoding.
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
Update Adobe Experience Manager to version 6.5.24 or later, or apply the vendor-supplied patch. Implement additional input validation and output encoding on affected form fields as a defense-in-depth measure.
AEM 6.5.24.0 or later; or AEM 2025.12.0 or later
- 1. Backup your current AEM instance and verify backup integrity before proceeding
- 2. Review the Adobe Experience Manager release notes for version 6.5.24.0 (or 2025.12.0 for cloud/early adopter releases) to understand changes and any migration requirements
- 3. Test the upgrade in a non-production environment first
- 4. Deploy the upgraded AEM 6.5.24.0 (or 2025.12.0) instance to production following your organization's change management process
- 5. Verify that the stored XSS vulnerability is remediated by testing the previously vulnerable form fields
- 6. Validate that custom code, integrations, and workflows function correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64580 — 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-64580 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