dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64600

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 · moderate confidence

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.23 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. When victims browse to pages containing the compromised fields, the malicious script executes in their browsers.

MitigationUpgrade to AEM 6.5.24 or later. Implement strict input validation and output encoding on all form fields to prevent script injection.

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. Determine AEM version
    Access the AEM Welcome page at /libs/granite/core/content/login.html or check the about page at /libs/cq/core/content/info.html. Alternatively, inspect the quickstart.properties file in crx-quickstart folder or the JAR file name in the installation directory.
    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 authored form components
    Navigate to /libs/foundation/components/form/ in the CRX/DE Lite (accessible at /crx/de) to inspect form component definitions. Look for any custom form field components or adaptive form configurations in your /apps directory.
    Affected if Form components are present and exposed to low-privileged users who can author content.
  3. Review form field input validation
    Examine the form field component JSP or HTL scripts in /apps for any custom input validation or output encoding logic. Check the server-side validation rules configured for adaptive forms or form containers.
    Affected if Form fields lack server-side input validation and proper output encoding is not applied when rendering submitted values.
  4. Identify low-privileged user access to forms
    Check which permission groups can access and author form pages. Review the permissions for the contributors or content-authors group in the User Administration console at /useradmin.
    Affected if Low-privileged users (such as content authors or contributors) have write access to form-enabled pages.

Your environment is affected if the installed AEM version is below 6.5.24.0 or below 2025.12.0 AND your forms accept user input from low-privileged accounts without proper validation.

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

Upgrade to AEM 6.5.24 or later. Implement strict input validation and output encoding on all form fields to prevent script injection.

Recommended fix High confidence

AEM 6.5.24.0 (for 6.5.x line) or AEM 2025.12.0 (for as-a-Cloud Service)

  1. 1. Identify the current Adobe Experience Manager version by checking the product information in the AEM Welcome page or system console.
  2. 2. For AEM 6.5.x deployments: Plan upgrade to version 6.5.24.0 or later.
  3. 3. For AEM as a Cloud Service deployments: Plan upgrade to version 2025.12.0 or later.
  4. 4. Review the Adobe Experience Manager release notes for the target version to understand changes and ensure compatibility with custom code.
  5. 5. Perform upgrade in a non-production environment first to validate functionality.
  6. 6. After testing, schedule maintenance window for production upgrade.
  7. 7. After upgrade, verify that the XSS vulnerability is resolved by testing the affected form fields.
Caveat Review Adobe release notes for the target version for any compatibility notes or deprecations affecting custom components or integrations

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
  • Testing12.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64600 — 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-64600 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