dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64802

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 in form fields. A low-privileged attacker can inject malicious JavaScript into vulnerable form inputs, which persists in the system and executes in victims' browsers when they view pages containing the affected fields.

MitigationApply the vendor patch by upgrading to AEM version 6.5.24 or later to resolve the XSS vulnerability in form field handling.

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 installed AEM version
    Access the AEM Web Console (system/console/systeminfo) or navigate to Help > About Adobe Experience Manager in the AEM UI to display the product version information
    Affected if The installed version is 6.5.23 or earlier, or falls within the 6.5.x line before 6.5.24.0, or is version 2025.12.0 or earlier (for the 2025 release track)
  2. Identify if AEM Forms module is deployed
    Check for the presence of AEM Forms add-on package by reviewing installed packages in Package Manager (etc/packages.html) or checking for /libs/fd namespace in the CRX/DE repository
    Affected if AEM Forms is installed and the AEM version is in the affected range above
  3. Review form container components in use
    Navigate to the Sites or Fragments consoles, open Page Editor, and inspect any Adaptive Form or Form Container components added to pages
    Affected if Form containers with user-input fields are present on published pages in an affected AEM version
  4. Inspect stored form data for malicious content
    Query the AEM repository (CRXDE Lite at /content/forms) or form data stores for unexpected script tags, javascript: URIs, or event handler attributes in submitted form data
    Affected if Malicious script content is found persisted in form submission data (indicates active exploitation)

Your environment is affected if AEM version 6.5.23 or earlier (or 6.5.x before 6.5.24.0, or 2025.12.0 or earlier) is running with AEM Forms or form container components enabled and exposed to 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 the vendor patch by upgrading to AEM version 6.5.24 or later to resolve the XSS vulnerability in form field handling.

Recommended fix High confidence

AEM 6.5.24.0 or later / AEM 2025.12.0 or later

  1. 1. Identify the current Adobe Experience Manager version by checking the product About page or system console
  2. 2. If running AEM 6.5.x version < 6.5.24.0, plan upgrade to 6.5.24.0 or later
  3. 3. If running the 2025.x release line, upgrade to 2025.12.0 or later
  4. 4. Review the Adobe Experience Manager release notes for the target version for any compatibility considerations
  5. 5. Perform the upgrade following Adobe's standard upgrade documentation
  6. 6. After upgrade, verify that the XSS vulnerability is resolved by testing form field inputs
  7. 7. Confirm the new version by checking the AEM About page
Caveat Review Adobe release notes for breaking changes between current version and target fixed version before upgrading

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
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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