CVE-2025-64574
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-privileged attacker can inject malicious JavaScript into vulnerable form fields, which persists in the system and executes when other users 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.
-
Check AEM product versionAccess the AEM Welcome page or use the system console (/system/console/status-productinfo) to view the installed Adobe Experience Manager version number.Affected if The installed version is 6.5.23 or earlier, or falls below 6.5.24.0, or is any 6.5.x version, or is below 2025.12.0 (cloud service).
-
Identify custom form components in useReview the content repository under /libs/fd/fm for custom form field configurations and check /content for pages containing Adaptive Forms or Core Components forms.Affected if Custom or out-of-the-box form fields are present in the AEM instance, as these are the injection points for the stored XSS.
-
Inspect form field content for malicious scriptsQuery the JCR (Java Content Repository) using tools like CRXDE Lite or the Query tool to search form field values containing script tags, javascript:, or on* event handlers (e.g., onload, onerror). Example JCR SQL2: SELECT * FROM [nt:unstructured] WHERE [value] LIKE '%<script%'Affected if Any form field content contains injected script tags or event handler attributes that were not authored by administrators.
-
Review low-privilege user permissionsNavigate to Tools > Security > Permissions or use the User Manager (/security/users.html) to examine which users have access to form authoring or content creation in form-enabled paths.Affected if Low-privileged users (non-admin) have write access to form fields or content paths, as these are the attackers who can inject the stored XSS.
A user is affected if their AEM installation version is 6.5.23 or earlier, or any 6.5.x version below 6.5.24.0, or below 2025.12.0 for cloud versions, AND the system has form fields accessible to low-privileged users that may contain injected malicious scripts.
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 a version newer than 6.5.23. Additionally, implement input validation and output encoding on form fields to prevent script injection.
6.5.24.0 or later (6.5.x branch)
- 1. Back up the current AEM instance including the repository, database, and configuration files.
- 2. Review the Adobe Experience Manager 6.5 Service Pack release notes at helpx.adobe.com for version 6.5.24.0 to understand any specific migration or configuration requirements.
- 3. Download Adobe Experience Manager 6.5.24.0 or later from the Adobe Software Distribution portal (if available) or apply the latest service pack through the AEM Package Manager.
- 4. Install the service pack following Adobe's standard installation procedure: stop the AEM instance, apply the package, restart the instance, and verify all bundles are active.
- 5. Clear the AEM HTML Library Manager cache and republish any affected content that contained vulnerable form fields.
- 6. Test the application to confirm the XSS vulnerability is remediated and that the form fields now properly sanitize user input.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.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 $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64574 — 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-64574 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