dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64613

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

MitigationUpgrade Adobe Experience Manager to version 6.5.24 or later. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure.

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 Adobe Experience Manager version
    Navigate to the AEM welcome page or access the system information via the Felix console at /system/console/bundles, or run: curl -s http://localhost:4502/crx/packmgr/service.jsp?cmd=ls 2>/dev/null | grep -i version. Alternatively, check the manifest.xml in the quickstart or the version.properties file in the crx-quickstart directory.
    Affected if The installed version is 6.5.23 or earlier, or falls within 6.5.x where x < 24, or is < 2025.12.0.
  2. Verify Forms or Adaptive Forms feature is in use
    Check if form-related content exists by querying the JCR repository at /content/forms/fp or by accessing the Forms UI at /aem/forms, or inspect the crx-quickstart/repository/var/audit folder for form-related audit events.
    Affected if Forms or Adaptive Forms functionality is enabled and form content exists in the repository.
  3. Inspect form field XSS protection configuration
    Review the form field XML configuration files under /content/forms/af or check the XSS protection config at /libs/cq/xssprotection or the HTL/Sightly template files used by forms for presence of proper encoding functions like escapeXSS or context-aware encoding.
    Affected if Form fields lack output encoding settings or input validation rules, or the XSS filter configuration is disabled or misconfigured.
  4. Check for existing malicious payloads in form data
    Query the JCR repository for suspicious script content in form submission nodes using a tool like CRXDE Lite at /content/forms/submissions or run a grep-like search: find /content/forms -type nt:file -exec grep -l '<script' {} \; or search for common XSS patterns in the repository.
    Affected if Stored malicious JavaScript payloads are found in form field data nodes.

A user is affected if their AEM version is below 6.5.24.0 or below 2025.12.0, Forms feature is enabled, and form fields are missing proper output encoding or contain injected malicious scripts.

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

Upgrade Adobe Experience Manager to version 6.5.24 or later. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure.

Recommended fix High confidence

Adobe Experience Manager 6.5.24.0 or later (6.5.x line); Adobe Experience Manager 2025.12.0 or later (Cloud Service)

  1. Identify the current Adobe Experience Manager version in use
  2. Download Adobe Experience Manager 6.5.24.0 or later from the official Adobe distribution channel
  3. Schedule a maintenance window and backup the current AEM instance
  4. Stop the AEM application server
  5. Install the updated AEM 6.5.24.0 package following Adobe's standard upgrade procedures
  6. Start the AEM instance and verify the application is running correctly
  7. Test that the stored XSS vulnerability is no longer present in form fields
  8. Deploy to production environment
Caveat Review Adobe's 6.5.24 release notes for any compatibility or configuration changes before upgrading

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
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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