dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64861

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-10
Fix available
A fix is available. Upgrade to 6.5.24.0 / 2025.12.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Adobe 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 confidence

Adobe Experience Manager versions 6.5.23 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability where low-privileged users can inject malicious JavaScript into form fields. When other users browse to pages containing these compromised fields, the malicious script executes in their browsers.

MitigationUpdate Adobe Experience Manager to a version newer than 6.5.23 to apply the security patch that addresses this stored XSS vulnerability.

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
Experience ManagerApplication
Affected:< 6.5.24.0< 2025.12.0= 6.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed AEM version
    Navigate to the AEM Welcome page or check the product.info in the system console (go to /system/console/systeminfo or check the 'About Adobe Experience Manager' option in the top-left hamburger menu). Note the exact version number displayed.
    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.
  2. Check for low-privileged user access to forms
    Review user group permissions in AEM to determine if non-admin users (contributors, authors, or other low-privilege groups) have write access to form components or custom form fields.
    Affected if Low-privileged users can edit or create form content in your AEM instance.
  3. Audit form field content for suspicious scripts
    Use AEM's search functionality or query the repository (via CRXDE Lite at /crx/de or the Query Builder) to search form-related content nodes for patterns like '<script', 'javascript:', 'onerror=', 'onload=', or other HTML/script tags stored in form field values.
    Affected if Any form fields contain encoded or raw script tags, event handlers (onerror, onload, onclick), or javascript: URIs that were not intentionally placed by administrators.
  4. Review recent content modifications by low-privilege users
    Check AEM's audit log or replication queue for recent changes to form content made by users in low-privilege groups. Access the audit log via the 'Audit' node in CRXDE or use the 'User Audit Reports' in the Tools section.
    Affected if Low-privilege users have recently modified form content, especially fields that should not contain HTML or script code.

Your environment is affected if the AEM version is 6.5.23 or earlier, any 6.5.x version below 6.5.24.0, or any version below 2025.12.0 AND low-privileged users have access to edit form fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.5.24.0 / 2025.12.0 or later
Fixed in 6.5.24.02025.12.0
Interim mitigation

Update Adobe Experience Manager to a version newer than 6.5.23 to apply the security patch that addresses this stored XSS vulnerability.

Recommended fix High confidence

AEM 6.5.24.0 or later, or AEM 2025.12.0 or later

  1. Identify the current Adobe Experience Manager version by checking the system information in the AEM console
  2. Schedule a maintenance window for the upgrade process
  3. Perform a complete backup of the AEM instance including the repository and database
  4. Upgrade Adobe Experience Manager to version 6.5.24.0 or later for the 6.5.x release train, OR upgrade to version 2025.12.0 or later for the newer release train
  5. Verify the upgrade completed successfully by checking the AEM version in the system console
  6. Validate that the XSS vulnerability is remediated by testing that malicious scripts can no longer be injected into form fields
  7. Review Adobe's upgrade documentation for any post-upgrade configuration requirements
Caveat Standard AEM upgrade considerations apply - review custom code compatibility, test third-party integrations, and verify content migrations in a non-production environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64861 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64861 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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