dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64553

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 compromised fields.

MitigationApply the vendor patch (upgrade AEM beyond version 6.5.23) and implement output encoding/sanitization on form fields to prevent script 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
    Access the AEM Web Console (typically at /system/console/bundles or /system/console/status-productinfo) to view the installed Adobe Experience Manager version. Alternatively, check the crx-quickstart/conf folder for version files or run 'java -jar quickstart.jar -version' if accessible.
    Affected if The installed version is 6.5.23 or earlier, or any 6.5.x version below 6.5.24.0, or any version below 2025.12.0, or the version matches exactly 6.5 with no specific patch level.
  2. Identify custom form components
    Navigate to the AEM Forms or Adaptive Forms interface (typically at /aem/forms.html or /libs/fd/af/components) and review custom form field components that accept user input. Check /apps and /libs directories for custom form field components.
    Affected if Custom form field components exist that allow user input without visible server-side output encoding or input validation configured.
  3. Inspect form field configuration
    Open the Edit dialog for key form fields and inspect their Properties panel. Look for validation patterns, allowed values, and whether 'Use HTML Encoding' or similar output encoding options are disabled or missing.
    Affected if Form field properties show no input validation rules or output encoding is explicitly disabled, allowing arbitrary content to be stored.
  4. Review stored form data in repository
    Access CRXDE Lite (at /crx/de) or use the Query Builder to search form submission nodes under /content/forms or /var/af/data. Examine stored values in the data store for unencoded script tags.
    Affected if Stored form submission data contains raw HTML tags, script elements, or event handlers (such as <script>, javascript:, onload, onerror) that were not sanitized on submission.

A user is affected if their AEM installation version falls within 6.5.23 or earlier, or below 6.5.24.0, or below 2025.12.0, AND their forms accept user input without proper output encoding, resulting in persisted 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

Apply the vendor patch (upgrade AEM beyond version 6.5.23) and implement output encoding/sanitization on form fields to prevent script execution.

Recommended fix High confidence

AEM 6.5.24.0 or later / AEM 2025.12.0 or later

  1. Check current Adobe Experience Manager version in use (via /system/console or AEM dashboard)
  2. Plan and schedule upgrade during a maintenance window
  3. Perform full backup of AEM instance including repository and database
  4. Upgrade AEM to version 6.5.24.0 or later, OR upgrade to 2025.12.0 or later release
  5. Verify the upgrade was successful by checking the new version number
  6. Test the fix by attempting to inject XSS payloads in vulnerable form fields to confirm the vulnerability is mitigated
  7. Deploy to production after successful testing
Caveat Point releases typically have minimal breaking changes; test thoroughly in staging environment before production deployment

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-64553 — 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-64553 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