CVE-2025-64578
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 in form fields. A low-privileged attacker can inject malicious JavaScript that persists in the form data and executes in victim users' browsers when they navigate to 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.
-
Determine installed AEM versionAccess the AEM Welcome page or check the product version via the system console at /system/console/configMgr or by viewing the manifest file in the installation directory. Compare the version number against the affected range: versions below 6.5.24.0 or version 6.5.x before 6.5.24 are vulnerable.Affected if The installed AEM version is 6.5.23 or earlier, or falls below 6.5.24.0 within the 6.5.x branch.
-
Identify if AEM Forms are in useNavigate to the AEM Forms console at /aem/forms or check for form-related content fragments or Adaptive Forms features. Look for form models in the CRXDE repository under /content/forms.Affected if Adobe Experience Manager Forms or Adaptive Forms features are enabled and actively used in the environment.
-
Audit form field input validation settingsExamine form container configurations in AEM Forms Author. Access the form editor, select form containers, and inspect the Validation and Properties settings for each form field to determine if input validation and output encoding are configured.Affected if Form fields lack input validation patterns or output encoding settings, allowing unsanitized user input to be stored.
-
Inspect stored form data for suspicious contentQuery the AEM repository (via CRXDE or the form data model) for form submissions stored under /content/forms or custom form data storage locations. Search for patterns matching script tags, javascript:, or other XSS vectors.Affected if Stored form data contains unsanitized HTML, script tags, or JavaScript event handlers that could execute in victim browsers.
-
Review low-privilege user access to formsCheck the user permissions for low-privileged accounts (such as content-authors or users with form-filling roles) in the AEM User Admin console at /security/users.html. Verify if these users can submit or edit form content without requiring approval.Affected if Low-privileged users have the ability to submit or modify form field content without sufficient sanitization or review.
The environment is affected if AEM version is below 6.5.24.0, AEM Forms with editable form fields are in use, and those form fields do not have input validation or output encoding enforced, allowing stored XSS payloads to persist.
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 version 6.5.24 or later to obtain the security patch. Additionally, implement input validation and output encoding on affected form fields as a defense-in-depth measure while the upgrade is being planned.
AEM 6.5.24.0 or later (6.5.x line) or AEM 2025.12.0 or later (continuous release)
- Identify the current Adobe Experience Manager version running in your environment
- Schedule a maintenance window and create a full backup of the AEM instance and content repository
- Test the upgrade in a staging environment before applying to production
- Upgrade Adobe Experience Manager to version 6.5.24.0 or later (for 6.5.x releases)
- Alternatively, upgrade to version 2025.12.0 or later if using the continuous release track
- After upgrade, verify the XSS fix is applied by testing the previously vulnerable form fields
- Clear AEM caches and rebuild any custom indexes if needed
- Monitor logs for any post-upgrade errors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64578 — 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-64578 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