dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64554

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

MitigationUpgrade Adobe Experience Manager to a version later than 6.5.23. Additionally, implement input validation and output encoding on form fields, and consider deploying Content Security Policy headers to mitigate XSS risks.

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 Adobe Experience Manager installed version
    Access the AEM System Information console at /system/console/system or check the version.properties file in the crx-quickstart directory. Alternatively, query the JMX MBean 'Adobe Experience Manager' via /system/console/jmx or use the AEM SDK script: 'java -jar aem-author.jar -version'. Compare the version number against the affected ranges: versions earlier than 6.5.24.0, earlier than 2025.12.0, or any 6.5.x release.
    Affected if The installed version is 6.5.23 or earlier, any 6.5.x version, or any version earlier than 2025.12.0.
  2. Identify custom form components that accept user input
    Review the /apps directory in CRX/DE (accessible at /crx/de) for custom form components under /apps that extend core form components (for example, form text fields, textareas, or hidden fields). Search for nodes containing ' granite:FormField' or 'sling:resourceType' references to custom form implementations.
    Affected if Custom form components exist that extend AEM's form framework without implementing input validation.
  3. Verify if form fields lack output encoding
    Examine the Sightly/JSP templates (.html files) rendering form input values. Check whether the Velocity or Sightly expression used to output form data uses context-aware encoding, such as ${formData @ context='html'} or equivalent XSS protection. Look for raw output of form fields in the HTL templates.
    Affected if Form field templates render user-submitted data without context-aware output encoding or sanitization.
  4. Check for unvalidated stored content in form-enabled pages
    Navigate to pages containing custom forms in the AEM Sites console. Submit test input containing script-safe characters (for example, <script>alert(1)</script>) into form fields. Then publish the page and view it as a non-privileged user to observe whether the script executes in the browser.
    Affected if Stored form submissions render without sanitization when viewed by other users.

If the installed AEM version is earlier than 6.5.24.0 or earlier than 2025.12.0 and custom form fields exist that accept user input without output encoding, the environment is affected by this stored XSS vulnerability.

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 a version later than 6.5.23. Additionally, implement input validation and output encoding on form fields, and consider deploying Content Security Policy headers to mitigate XSS risks.

Recommended fix High confidence

6.5.24.0 or later (or 2025.12.0 or later)

  1. Upgrade Adobe Experience Manager to version 6.5.24.0 or later
  2. Alternatively, upgrade to version 2025.12.0 or later if using the newer release cadence
  3. After upgrade, verify the fix by testing the previously vulnerable form fields for XSS payloads
  4. Confirm that stored XSS payloads are no longer executed in victim browsers

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
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
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,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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