dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64797

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-privilege attackers to inject malicious JavaScript into form fields. The malicious payload persists in the system and executes in victim users' browsers when they view pages containing the compromised form fields.

MitigationUpdate Adobe Experience Manager to a version newer than 6.5.23, or implement server-side input validation and output encoding on affected 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. Identify installed AEM version
    Access the AEM system information page at /system/console/about or query the version endpoint at /libs/cq/core/content/info.json. Locate the version number in the response.
    Affected if The installed version is 6.5.23 or earlier, equals 6.5, or is below 2025.12.0.
  2. Verify AEM 6.5 service pack level
    Navigate to Help > System Information in the AEM welcome page, or check the installed service pack via the Felix Console at /system/console/bundles to confirm the exact 6.5.x build number.
    Affected if The service pack version is below 6.5.24.0.
  3. Confirm form creation functionality is accessible
    Check if low-privilege users (such as those with only content-author or contributor roles) can access the Forms functionality at /aem/forms or create form containers within AEM Sites.
    Affected if Low-privilege users can create or edit form components in AEM.
  4. Review existing form field data for suspicious content
    Query the AEM repository (via CRXDE Lite at /crx/de or the Query tool) for form field nodes under /content and inspect stored values for unusual script tags, event handlers, or encoded JavaScript patterns.
    Affected if Form field data contains unsanitized HTML or script tags that could execute in a browser.
  5. Inspect form field input validation settings
    Access the Form Component dialog configuration for affected forms and check whether server-side input validation and output encoding are explicitly enabled on each form field.
    Affected if Form fields lack server-side validation and rely solely on client-side or no input sanitization.

Your environment is affected if the installed AEM version falls within the vulnerable ranges AND low-privilege users can inject content into form fields without server-side validation catching the payload.

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 a version newer than 6.5.23, or implement server-side input validation and output encoding on affected form fields to prevent script injection.

Recommended fix High confidence

Adobe Experience Manager 6.5.24.0 or Adobe Experience Manager 2025.12.0

  1. Review the current Adobe Experience Manager version installed in your environment
  2. Download Adobe Experience Manager 6.5.24.0 (for AEM 6.5 on-premise) or 2025.12.0 (for AEM as a Cloud Service) from the official Adobe distribution portal
  3. Plan and schedule a maintenance window for the upgrade following Adobe's recommended upgrade best practices
  4. Back up all AEM repositories, configurations, and custom code before proceeding
  5. Perform the upgrade in a non-production environment first to validate compatibility
  6. After successful testing in non-production, apply the upgrade to production environments
  7. Verify the upgrade was successful by checking the AEM version in the Help > About Adobe Experience Manager console
  8. Validate that custom form components and user-generated content workflows function correctly post-upgrade

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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