Skip to main content
VulnerabilityPublished

CVE-2025-61796: Adobe Experience Manager · Cross-site Scripting

Affects Adobe Experience ManagerSource CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Adobe Adobe Experience ManagerAffected
  • =0
Fixed in–

AI-suggested

  1. Monitor Adobe’s official channels for patches addressing CVE-2025-61796 and apply them promptly once available.
  2. Implement strict input validation and output encoding on all user-supplied data in AEM forms to prevent injection of malicious scripts.
  3. Deploy Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of XSS attacks.
  4. Conduct regular security audits and penetration testing focused on web application vulnerabilities, including XSS.
  5. Educate users and administrators about the risks of clicking on suspicious links and encourage cautious behavior to reduce the likelihood of successful social engineering.
  6. Utilize web application firewalls (WAFs) with rules designed to detect and block XSS payloads targeting AEM.
  7. Limit privileges of users who can submit data to vulnerable forms to reduce the attack surface.
  8. Review and harden AEM configurations to disable or restrict features that may facilitate script injection.
  9. Implement logging and monitoring to detect unusual activities that may indicate exploitation attempts.

Description

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.

References

Community reviews

Loading reviews…