dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64881

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

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. The malicious payload persists in the system and executes in victims' browsers when they navigate to pages containing the affected fields.

MitigationUpdate Adobe Experience Manager to version 6.5.24 or later, or apply the vendor-provided security patch to address the 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. Check Adobe Experience Manager version
    Locate the AEM version file - typically found in the crx-quickstart/launch.properties or version.properties file in the AEM installation directory. Open the file and locate the version number entry.
    Affected if The installed version is 6.5.23 or earlier, or exactly 6.5, or any version prior to 2025.12.0 (for example, 6.5.22, 6.5.21, etc.)
  2. Identify AEM service pack version
    Access the AEM Web Console Bundles page at /system/console/bundles or check the About Adobe Experience Manager page at /libs/granite/ui/content/shell/about.html to confirm the exact service pack level.
    Affected if The service pack version shown is below 6.5.24.0
  3. Verify presence of form components accepting user input
    Review the AEM instance for any published forms, comment fields, contact forms, user registration forms, or custom form components that accept user-submitted data. Check the CQ/Granite form components in the content structure.
    Affected if The environment contains forms or form fields that accept and store user input, particularly in the /content directory or form containers.
  4. Inspect stored form data for malicious payloads
    Use CRXDE Lite (accessible at /crx/de) or the AEM Query Builder to search the repository for common XSS payloads in form field content nodes. Look for script tags, javascript: URIs, or event handlers in stored values.
    Affected if Any form field content in the repository contains injected script tags or JavaScript event handlers (such as onload, onerror, onmouseover) in stored values.

You are affected if your AEM installation is version 6.5.23 or earlier, or exactly version 6.5, or any version below 2025.12.0, AND your environment has forms that accept user input where malicious scripts could be stored and later rendered.

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 version 6.5.24 or later, or apply the vendor-provided security patch to address the stored XSS vulnerability.

Recommended fix High confidence

6.5.24.0 (or later 6.5.x release) / 2025.12.0 (or later)

  1. Identify the current Adobe Experience Manager version installed in the environment
  2. Consult Adobe documentation (helpx.adobe.com) for the specific upgrade procedure for your deployment model
  3. Ensure a complete backup of the AEM instance and content repository is performed before upgrading
  4. Upgrade Adobe Experience Manager to version 6.5.24.0 or later for the 6.5.x release line, OR upgrade to 2025.12.0 or later for the newer release line
  5. After upgrade, verify the XSS vulnerability is resolved by testing that malicious scripts can no longer be stored in form fields
  6. Confirm all custom code and third-party integrations function correctly post-upgrade
Caveat Point releases typically have minimal breaking changes; review Adobe's release notes for 6.5.24.0 for any compatibility notes

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
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,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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