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.
Security readout for executives and security teams
Plain-English summary
A low-privileged user could save malicious script content in certain Adobe Experience Manager form fields. The script may run when another person views the affected page, potentially exposing or altering limited information within that user’s browser session. Exploitation requires both authenticated low-level access and victim interaction.
Executive priority
Schedule remediation through normal vulnerability-management timelines, prioritizing externally accessible or broadly authored AEM environments. Escalate where low-privileged accounts are numerous, untrusted users can submit content, or administrators commonly view submitted pages. Current evidence does not justify emergency incident status by itself.
Technical view
CVE-2026-27249 is stored cross-site scripting (CWE-79) with CVSS 3.1 score 5.4. It is network-accessible, low complexity, requires low privileges and user interaction, and changes security scope. Expected impact is limited confidentiality and integrity loss without availability impact.
Likely exposure
Exposure exists where listed AEM versions are deployed and low-privileged users can submit content to vulnerable form fields viewed by others. The bundle identifies AEM 6.5.23 and earlier, Cloud Service through 2026.2.0, and 6.5 LTS through SP2; confirm exact applicability with Adobe.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Practical abuse requires a low-privileged attacker to store malicious content and persuade or wait for a victim to view the affected page.
Researcher notes
The vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. Scope change indicates browser-executed script may cross the vulnerable component’s security boundary. The supplied version representation is condensed and potentially ambiguous, so researchers should use Adobe APSB26-24 as the authoritative source for exact release boundaries.
Mitigation direction
Inventory Adobe Experience Manager deployments and record exact product editions and versions.
Review Adobe advisory APSB26-24 for the applicable vendor-supported update.
Upgrade affected deployments beyond the identified vulnerable release according to Adobe guidance.
Restrict low-privileged content submission until remediation if operationally feasible.
Monitor AEM content changes and browser-facing security alerts for suspicious stored scripts.
Validation and detection
Confirm each deployment’s edition and version against Adobe APSB26-24.
Verify the vendor-recommended update completed successfully on every affected instance.
Review access controls governing users who can submit or modify form content.
Inspect recently modified form content for unexpected scripts or event-handler markup.
Use authorized defensive testing to confirm submitted content is safely handled after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.