CVE-2025-64559
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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.23 and earlier allows low-privileged authenticated users to inject malicious JavaScript into form fields. The payload persists in the system and executes in victims' browsers when they 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.
-
Determine AEM versionAccess the AEM Welcome page (http://[host]:[port]/aem/start.html) and locate the version information in the bottom-left corner, or check the version.properties file in the crx-quickstart folder.Affected if The installed version is 6.5.23 or earlier, any 6.5.x version below 6.5.24.0, or any version below 2025.12.0.
-
Identify AEM Forms usageNavigate to the Forms section in AEM by accessing http://[host]:[port]/aem/forms.html, or check if form-related packages (com.adobe.aemds-* or forms-related bundles) are installed via the OSGi Console at http://[host]:[port]/system/console/bundles.Affected if AEM Forms or Adaptive Forms functionality is enabled and accessible in the environment.
-
Verify form field input handlingAs a low-privileged user (e.g., with 'forms-user' or 'content-author' role), create or edit an Adaptive Form or Form Fragment and attempt to insert HTML/JavaScript content into a text field, then save and preview the form.Affected if The system allows submission of unescaped HTML or script content into form fields without sanitization.
-
Check user group permissionsNavigate to http://[host]:[port]/security/useradmin.html or use the User Management console to review permissions assigned to low-privilege groups, specifically checking if these groups have access to create or edit Adaptive Forms.Affected if Low-privileged authenticated users (non-admin) have permissions to create, edit, or submit Adaptive Forms.
-
Inspect form submission storageReview the JCR (Jackrabbit) repository at /content/forms/fp or use CRXDE to inspect stored form data at /content/forms/af for any existing form submissions containing raw HTML script tags.Affected if Stored form data contains unsanitized script tags or HTML that would execute when rendered.
You are affected if your AEM version is below 6.5.24.0 or below 2025.12.0 AND AEM Forms with user-editable fields is enabled and accessible to low-privileged users.
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, or implement strict input validation and output encoding on all form fields as a compensating control.
AEM 6.5.24.0 or later; AEM Cloud Service 2025.12.0 or later
- 1. Identify your current Adobe Experience Manager version by checking the product console or system information
- 2. For AEM 6.5.x on-premises: Plan upgrade to version 6.5.24.0 or later
- 3. For AEM Cloud Service: Ensure your environment is updated to 2025.12.0 or later
- 4. Before upgrading, review the Adobe Experience Manager release notes for version 6.5.24.0 to check for any compatibility notes
- 5. Perform the upgrade following Adobe's standard upgrade procedures for your deployment type
- 6. After upgrade, verify the XSS protection is properly applied by testing form fields that could accept user input
- 7. Ensure your AEM instance is running the latest available service pack within the 6.5.24+ line for ongoing security updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64559 — 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-64559 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