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 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 allowing limited actions as that user. Successful exploitation requires victim interaction.
Executive priority
Treat this as a moderate, prompt-remediation issue rather than an emergency. Accelerate action for internet-facing AEM environments, untrusted contributor access, or pages commonly viewed by administrators. Business impact is primarily limited session or data exposure and unauthorized browser-level actions, not service outage.
Technical view
CVE-2026-27253 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, changes security scope, and has low confidentiality and integrity impact without availability impact.
Likely exposure
The description identifies Adobe Experience Manager 6.5.23 and earlier. Exposure is more likely where low-privileged or untrusted users can populate vulnerable form fields and other users view the resulting pages. The bundle also lists Cloud Service and 6.5 LTS boundaries, but their status representation is ambiguous; confirm applicability with Adobe.
Exploitation context
The bundle provides no evidence of active exploitation, and the CVE is not listed as KEV. Exploitation requires an attacker with low privileges to store script content and a victim to browse the affected page. Risk increases when administrators or other sensitive users view attacker-influenced content.
Researcher notes
The CVSS vector is AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. Testing should focus on stored output encoding and sanitization boundaries for form fields, using harmless validation content in authorized staging environments. The bundle’s normalized affected-version entries are not sufficiently clear to assert exact Cloud Service or LTS cutoffs.
Mitigation direction
Review Adobe advisory APSB26-24 and apply the vendor-recommended update or remediation for each deployment model.
Restrict low-privileged access to affected form-authoring or content-submission features until remediation is complete.
Review stored form content for unexpected scripts, event handlers, or other active browser content.
Prioritize internet-facing instances and environments where untrusted contributors can create content.
Validation and detection
Inventory AEM deployment models and versions, specifically identifying 6.5.23 and earlier installations.
Confirm affected version boundaries and remediation requirements against Adobe advisory APSB26-24.
Identify form fields writable by low-privileged or untrusted accounts and determine where their content is rendered.
After remediation, verify in staging that stored field content cannot execute active browser content.
Review relevant content changes and access logs for suspicious low-privileged submissions.
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.