Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-27240: Cross-site Scripting (Stored XSS) (CWE-79) in Adobe Adobe Experience Manager

0
Medium
VulnerabilityCVE-2026-27240cvecve-2026-27240cwe-79
Published: Wed Mar 11 2026 (03/11/2026, 00:23:20 UTC)
Source: CVE Database V5
Vendor/Project: Adobe
Product: Adobe Experience Manager

Description

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.

AI-Powered Analysis

AILast updated: 03/11/2026, 01:21:03 UTC

Technical Analysis

CVE-2026-27240 is a stored Cross-Site Scripting (XSS) vulnerability identified in Adobe Experience Manager (AEM) versions 6.5.23 and earlier. The vulnerability arises from insufficient input sanitization in certain form fields, allowing an attacker with low privileges to inject malicious JavaScript code that is persistently stored on the server. When other users access the affected pages containing the injected scripts, the malicious code executes in their browsers within the security context of the vulnerable web application. This can lead to unauthorized actions such as session hijacking, credential theft, or unauthorized modifications of displayed content. The vulnerability has a CVSS v3.1 base score of 5.4, indicating medium severity, with an attack vector of network (remote exploitation), low attack complexity, requiring low privileges, and user interaction to trigger the exploit. The scope is changed, meaning the vulnerability affects resources beyond the initially vulnerable component. No public exploits have been reported yet, but the nature of stored XSS makes it a significant risk in environments where AEM is used to manage web content accessible by multiple users. The vulnerability is tracked under CWE-79, a common and well-understood class of web application security issues. Adobe has not yet published patches or mitigation instructions at the time of this report, so organizations must rely on interim controls.

Potential Impact

The impact of this vulnerability is primarily on confidentiality and integrity. An attacker exploiting this stored XSS flaw can execute arbitrary JavaScript in the context of other users' browsers, potentially stealing session cookies, performing actions on behalf of users, or defacing web content. This can lead to unauthorized access to sensitive information, user impersonation, and reputational damage. Although availability is not directly affected, the indirect consequences of compromised user sessions or defaced content can disrupt business operations. Organizations using AEM for critical web content delivery, especially those with many users or sensitive data, face increased risk. The requirement for user interaction (visiting a maliciously crafted page) limits exploitation somewhat, but the persistent nature of stored XSS increases the attack surface. The medium CVSS score reflects these factors, but the real-world impact could escalate if combined with social engineering or other attack vectors.

Mitigation Recommendations

Organizations should immediately review their Adobe Experience Manager deployments and identify versions 6.5.23 and earlier. Since no official patches are currently available, interim mitigations include: 1) Implement strict input validation and output encoding on all user-supplied data, especially in form fields susceptible to injection. 2) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts. 3) Use web application firewalls (WAFs) with rules targeting XSS payloads to detect and block malicious requests. 4) Educate users to recognize suspicious links or content that could trigger XSS attacks. 5) Limit privileges of users who can submit content to reduce the risk of malicious input. 6) Monitor logs and user activity for signs of exploitation attempts. Once Adobe releases official patches, prioritize timely deployment to fully remediate the vulnerability. Additionally, conduct security testing and code reviews to identify and fix similar injection points.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
adobe
Date Reserved
2026-02-18T22:02:41.382Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69b0be892f860ef943f0dcff

Added to database: 3/11/2026, 12:59:53 AM

Last enriched: 3/11/2026, 1:21:03 AM

Last updated: 3/13/2026, 12:08:45 AM

Views: 10

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses