CVE-2026-27231
MediumCVSS 5.4Exploitation Probability (EPSS)
Low risk11th percentile - higher than 11% of all known CVEs
Summary
Adobe Experience Manager versions 6.5.23 and earlier are affected by a stored XSS vulnerability. An attacker can 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.
Risk Assessment
An attacker could steal session data or take over user accounts when victims visit the compromised page. This may lead to confidentiality breaches and system integrity issues.
Recommendation
Update Adobe Experience Manager to the latest patched version. Apply input validation and restrict user privileges.
Other vulnerabilities in Adobe Experience Manager
See all- CVE-2017-3111High
An issue was discovered in Adobe Experience Manager versions 6.3, 6.2, 6.1, and 6.0, where sensitive tokens are included in HTTP GET requests under certain circumstances.
- CVE-2017-3110High
Adobe Experience Manager 6.1 and earlier has a sensitive data exposure vulnerability.
- CVE-2017-3107High
Adobe Experience Manager 6.3 and earlier has a misconfiguration vulnerability.
- CVE-2016-7885High
Adobe Experience Manager versions 6.2 and earlier have a vulnerability that could be used in Cross-Site Request Forgery attacks.
- CVE-2016-0958High
Adobe Experience Manager versions 5.6.1, 6.0.0, and 6.1.0 may allow remote attackers to have an unspecified impact via a crafted serialized Java object.
- CVE-2026-48359Critical
Adobe Experience Manager is affected by an Improper Restriction of XML External Entity Reference ('XXE') vulnerability that could result in arbitrary code execution in the context of the current user. A low-privileged attacker could exploit this vulnerability to read sensitive files, potentially gaining elevated access or control over the victim's account or session. Exploitation of this issue does not require user interaction. Scope is changed.
- CVE-2026-48259Critical
Adobe Experience Manager is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in arbitrary code execution in the context of the current user. A low-privileged attacker could leverage this vulnerability to issue unauthorized server-side requests, potentially gaining elevated access or control over the victim's account or session. Exploitation of this issue does not require user interaction and the scope is changed.
- CVE-2025-64539Critical
Adobe Experience Manager versions 6.5.23 and earlier are affected by a DOM-based XSS vulnerability that could lead to arbitrary code execution. An attacker could inject malicious scripts into a web page that execute in the victim's browser. Successful exploitation could lead to session takeover, increasing confidentiality and integrity impact. User interaction is required – the victim must visit a crafted page.
- CVE-2025-64538Critical
Adobe Experience Manager versions 6.5.23 and earlier are affected by a DOM-based XSS vulnerability that could lead to arbitrary code execution. An attacker could inject malicious scripts into a web page that execute in the victim's browser. Successful exploitation could lead to session takeover, increasing confidentiality and integrity impact. User interaction is required – the victim must visit a crafted page.
- CVE-2025-64537Critical
Adobe Experience Manager versions 6.5.23 and earlier are affected by a DOM-based XSS vulnerability that could lead to arbitrary code execution. An attacker could inject malicious scripts into a web page that execute in the victim's browser. Successful exploitation could lead to session takeover, increasing confidentiality and integrity impact. User interaction is required – the victim must visit a crafted page.
Original NVD description (English source)
Adobe Experience Manager versions 6.5.23 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by an 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.