dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64800

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

A stored 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 injected script persists on the server and executes in the browsers of users who view pages containing the compromised form fields.

MitigationApply Adobe's official patch by upgrading Adobe Experience Manager to version 6.5.24 or later, which 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. Determine installed AEM version
    Access the AEM Web Console or system console (typically at /system/console/bundles or /system/console/webconsole) to view the installed product version, or check the quickstart properties file in the AEM installation directory
    Affected if The installed version is 6.5.23 or earlier, or any version before 2025.12.0, indicating the vulnerability is present in the baseline version
  2. Verify low-privileged user access to forms
    Review user group memberships and permissions in AEM to identify users with contributor or author-level access (not admin) who can access and edit form components
    Affected if Low-privileged authenticated users have write access to form fields, which would allow them to inject malicious scripts
  3. Inspect stored form data for injected scripts
    Query the AEM repository (via CRXDE Lite at /crx/de or using the Query tool) for form field content nodes and inspect stored values for suspicious patterns such as <script> tags, javascript: URIs, or HTML event handlers (onclick, onerror, etc.)
    Affected if Any form field values contain unescaped script tags, event handlers, or javascript: protocol URIs that could execute in user browsers
  4. Review recent form submission history
    Check the AEM workflow or form submission logs for recent entries, or examine the content repository under /content/forms for any forms with unexpected or encoded content in field values
    Affected if There are recent form submissions containing encoded or obfuscated content that may represent attempted XSS injection

Your environment is affected if the installed AEM version is earlier than 6.5.24.0 or earlier than 2025.12.0 AND low-privileged users have the ability to modify form field content that gets stored and displayed to other users.

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

Apply Adobe's official patch by upgrading Adobe Experience Manager to version 6.5.24 or later, which addresses this stored XSS vulnerability.

Recommended fix High confidence

AEM 6.5.24.0 or later

  1. Check current Adobe Experience Manager version in use (Help > About Adobe Experience Manager)
  2. Review the AEM 6.5.24.0 release notes for any pre-upgrade requirements or migration steps
  3. Create a full backup of the AEM instance including repository, database, and configurations
  4. Test the upgrade in a non-production environment first
  5. Apply the upgrade to AEM 6.5.24.0 or later release
  6. Verify the upgrade was successful by checking the version number
  7. Clear browser cache and test that the application functions normally
  8. Validate that the XSS vulnerability is patched by attempting to inject script in the previously affected form fields
Caveat Standard AEM upgrade considerations apply - review release notes for any deprecated features or configuration changes that may require adjustment

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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