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.
Security readout for executives and security teams
Plain-English summary
An authenticated, low-privilege attacker could save malicious JavaScript in an Adobe Experience Manager form field. The script may run when another user views the affected page, potentially exposing limited browser-accessible information or enabling limited actions as that user. Exploitation requires both content submission access and victim interaction.
Executive priority
Address through the normal vulnerability-remediation cycle, accelerating internet-facing or broadly authored AEM environments. The moderate score and required victim interaction reduce urgency relative to unauthenticated compromise, but stored content can repeatedly affect privileged viewers until removed.
Technical view
CVE-2026-27231 is stored XSS (CWE-79) in Adobe Experience Manager. It is remotely reachable, low complexity, requires low privileges and user interaction, and crosses a security boundary. CVSS 3.1 is 5.4 (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), with no availability impact identified.
Likely exposure
Exposure depends on the deployed AEM edition and version, whether untrusted or lower-privileged users can populate vulnerable form fields, and whether other users view that content. The bundle’s version entries and description are inconsistent, so confirm affected releases against Adobe’s advisory rather than relying solely on the supplied ranges.
Exploitation context
The bundle does not establish active exploitation, and the CVE is not listed as KEV. Abuse requires an attacker with low privileges to store script content and a victim to visit the resulting page. No evidence supplied here establishes public exploit availability or observed attacks.
Researcher notes
The source description says AEM 6.5.23 and earlier, while the structured affected data includes boundaries labeled 6.5.24, LTS SP2, and Cloud Service 2026.2.0 with unclear range semantics. Treat Adobe APSB26-24 as authoritative for product-specific applicability. The supplied evidence supports stored XSS, not server compromise.
Mitigation direction
Consult Adobe advisory APSB26-24 and apply the applicable vendor update or remediation.
Prioritize internet-facing AEM instances accepting content from lower-privileged or untrusted users.
Restrict form-field authoring permissions until remediation is verified.
Review stored form content for unexpected scripts or event-handler markup.
Validation and detection
Inventory each AEM deployment, edition, version, exposure, and authoring role.
Compare installed versions directly with Adobe advisory APSB26-24.
Confirm lower-privileged accounts cannot store executable browser content in affected fields.
Review content changes and security telemetry for suspicious stored markup.
After remediation, verify previously stored malicious content cannot execute when viewed.
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.