Browser script execution via stored form input
Published Dec 10, 2025 · Updated Dec 10, 2025
Stored XSS in Adobe Experience Manager 6.5.23 and earlier allows remote authenticated users to run script in a victim's browser. AEM stores attacker-supplied script in an unspecified vulnerable form field and later renders the value without adequate neutralization; Adobe has not identified the field or implementation locus. Low-privileged access is sufficient to plant the payload, but execution requires a victim to visit the affected page and is confined to that browser context.
Summary
What happened
Stored XSS in Adobe Experience Manager 6.5.23 and earlier allows remote authenticated users to run script in a victim's browser. AEM stores attacker-supplied script in an unspecified vulnerable form field and later renders the value without adequate neutralization; Adobe has not identified the field or implementation locus. Low-privileged access is sufficient to plant the payload, but execution requires a victim to visit the affected page and is confined to that browser context.
The record
- CVE
- CVE-2025-64578
- Published
- Dec 10, 2025
- Updated
- Dec 10, 2025
- Vendor
- Adobe
- Product
- Adobe Experience Manager
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 10, 2025CVE publishedPublication date reported by the CVE source.
- Dec 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=6.5.23
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo