dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-61796

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 11.6 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. Exploitation of this issue requires user interaction in that a victim must open a malicious link. Scope is changed.

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 · moderate confidence

Adobe Experience Manager versions 11.6 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability where low-privileged attackers can inject malicious JavaScript into vulnerable form fields. When victims view pages containing these compromised fields, the malicious script executes in their browsers.

MitigationApply the vendor patch for CVE-2025-61796 when available, and implement input validation and output encoding on all 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.22.0

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
    Navigate to AEM Welcome page > Help > Version, or access /system/console/systeminfo to view the product version. Compare the version number to the affected range (6.5.22.0 and earlier, or versions 11.6 and earlier).
    Affected if The installed AEM version is 6.5.22.0 or earlier, or falls within the 11.6 and earlier range.
  2. Locate form components in use
    Review the AEM content structure under /content or /apps for form-related components such as core form components, foundation form components, or custom form implementations.
    Affected if Form components are present and actively used in the AEM instance.
  3. Examine form field configurations for untrusted input
    Access the form field component dialogs (via CRX/DE or the AEM Forms UI) and review the allowed values, default values, and validation patterns configured for text input fields, textareas, and similar components.
    Affected if Form fields accept free-text input without documented input validation or output encoding controls.
  4. Inspect stored form data for malicious scripts
    Query the repository (via CRX/DE Lite or the Query Builder) for stored form submission data and review field values for script tags, javascript: handlers, or event attributes like onload, onerror.
    Affected if Form data contains HTML script tags, JavaScript event handlers, or encoded script payloads in field values.

If the AEM version is 6.5.22.0 or earlier (or within 11.6 and earlier), form components are in use, and malicious scripts are found in form field configurations or stored data, 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch for CVE-2025-61796 when available, and implement input validation and output encoding on all form fields to prevent script injection.

Recommended fix Moderate confidence

AEM 6.5 Service Pack 23 or later

  1. 1. Navigate to the Adobe Software Distribution portal (https://experience.adobe.com/) and download the latest AEM 6.5 Service Pack release.
  2. 2. Review the release notes for the new service pack to confirm inclusion of security fixes for CVE-2025-61796.
  3. 3. Back up your current AEM instance including content repository, configurations, and any custom code.
  4. 4. Install the new AEM 6.5 Service Pack on a non-production environment first to validate compatibility.
  5. 5. After successful testing, schedule a maintenance window and install the update on production.
  6. 6. Verify that the update was successful by logging into AEM and checking the version in the About Adobe Experience Manager page.
  7. 7. Test critical workflows and forms to ensure the XSS fix does not impact legitimate functionality.
Caveat Service pack upgrades typically require thorough testing of custom components and workflows; review Adobe's 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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