Skip to main content
CVE-2025-64627VulnerabilityPublished

CVE-2025-64627: Adobe Experience Manager · Cross-site Scripting (Stored XSS)

Affects Adobe Experience ManagerSource CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 06:26 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 16% 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 10 Dec 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 2026-10-26.

What to do

Affected software

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

AI-suggested

To mitigate CVE-2025-64627 effectively, organizations should implement a multi-layered approach beyond generic advice. First, apply strict input validation on all form fields to ensure that only expected data types and formats are accepted, rejecting or sanitizing any suspicious input. Second, implement robust output encoding or escaping mechanisms on all user-supplied content before rendering it in the browser to prevent script execution. Third, employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of any injected code. Fourth, restrict the use of vulnerable form fields or disable them if not essential, minimizing the attack surface. Fifth, monitor web application logs and user activity for unusual patterns indicative of attempted exploitation. Sixth, educate users and administrators about the risks of XSS and encourage cautious behavior when interacting with web content. Finally, stay alert for official Adobe patches or updates addressing this vulnerability and deploy them promptly once available. If immediate patching is not possible, consider implementing web application firewalls (WAFs) with custom rules to detect and block malicious payloads targeting the vulnerable fields. Regular security assessments and penetration testing focused on XSS vulnerabilities can help identify and remediate similar issues proactively.

Description

CVE-2025-64627 is a stored Cross-Site Scripting (XSS) vulnerability affecting Adobe Experience Manager (AEM) versions 6.5.23 and earlier. A low privileged attacker can inject malicious JavaScript into vulnerable form fields, which executes in the browsers of users who visit the affected pages. This vulnerability requires user interaction to trigger and does not allow direct system compromise but can lead to session hijacking, data theft, or further attacks within the context of the victim's browser. The CVSS score is 5.4 (medium severity), reflecting the moderate impact and ease of exploitation with low privileges. No known exploits are currently in the wild, and no patches have been linked yet. European organizations using AEM, especially in countries with high adoption of Adobe products in government, media, and enterprise sectors, should prioritize mitigation. Mitigations include input validation, output encoding, and restricting form field usage, along with monitoring and applying updates once available.

References

Community reviews

Loading reviews…