dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64852

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 payload persists in the system and executes when victims browse to pages containing the affected form fields.

MitigationApply the AEM security patch (6.5.24 or later). Until patched, implement input validation/sanitization on vulnerable form fields and enforce Content Security Policy (CSP) headers to mitigate XSS execution.

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 AEM version
    Log into AEM as administrator and navigate to Help > About Adobe Experience Manager, or access the system console at /system/console/configMgr and look for the Product Version information. Alternatively, check the crx-quickstart/manifest.mf file for the version number.
    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. Identify exposed form components
    Review the AEM instance for publicly accessible forms that accept user input, such as Adaptive Forms, core form components, or custom form implementations. Check the content structure under /content or /etc for form pages.
    Affected if The AEM instance exposes any form-based pages or components that accept user input without server-side validation.
  3. Inspect form field data for malicious payloads
    Query the JCR repository using CRXDE Lite (at /crx/de) or the Query Builder API to search for stored form submissions. Look for patterns like <script>, javascript:, onerror=, or other XSS vectors in form-related nodes under /content/forms, /content/dam, or custom form containers.
    Affected if Any form field data contains encoded or raw JavaScript injection attempts in the repository.
  4. Review recent content changes
    Access the AEM Workflow inbox or use the Replication queue to identify recent content publications. Check the audit log at /var/audit for entries related to form submissions and user-created content.
    Affected if There are recent form submission entries from low-privileged users that may contain injected scripts.

The environment is affected if the installed AEM version is 6.5.23 or earlier, any 6.5 version below 6.5.24.0, or any version below 2025.12.0, AND the instance exposes accessible form components that accept user input.

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 AEM security patch (6.5.24 or later). Until patched, implement input validation/sanitization on vulnerable form fields and enforce Content Security Policy (CSP) headers to mitigate XSS execution.

Recommended fix High confidence

6.5.24.0 or later (or 2025.12.0 or later for the newer release train)

  1. Identify the current Adobe Experience Manager version by checking the product UI or system information
  2. Download Adobe Experience Manager 6.5.24.0 or later from the official Adobe distribution repository
  3. Review the Adobe Experience Manager upgrade documentation for your specific deployment type
  4. Schedule a maintenance window and create a full backup of the AEM instance and content repository
  5. Test the upgrade in a staging environment before applying to production
  6. Deploy the upgrade to production during the maintenance window
  7. Verify the upgrade was successful by checking the AEM version in the About Adobe Experience Manager page
  8. Clear all AEM caches and republished content that may contain the vulnerable form fields
Caveat Patch releases typically have minimal breaking changes; however, always review the AEM 6.5.24.0 release notes for any specific compatibility notes before upgrading

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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