Adobe Experience Manager versions 6.5.24, FP11.7 and earlier are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability. An attacker could exploit this issue by manipulating the DOM environment to execute malicious JavaScript within the context of the victim's browser. Exploitation of this issue requires user interaction in that a victim must visit a specially crafted web page.
Security readout for executives and security teams
Plain-English summary
This flaw can let an attacker run malicious JavaScript in a victim’s browser through a vulnerable Adobe Experience Manager deployment. The victim must visit a specially crafted page, limiting immediacy, but successful exploitation could expose or alter browser-accessible information within the affected site’s context.
Executive priority
Treat this as a normal-priority security update with timely remediation. User interaction, low impacts, and no reported availability effect reduce urgency, but browser-based data exposure or unauthorized actions remain possible. Prioritize externally reachable or sensitive AEM environments and deployments used by privileged personnel.
Technical view
CVE-2026-34623 is a DOM-based XSS vulnerability classified as CWE-79. The supplied narrative identifies AEM 6.5.24, FP11.7, and earlier as affected. CVSS 3.1 scores it 5.4: network-accessible, low complexity, low privileges, user interaction required, changed scope, low confidentiality and integrity impact, and no availability impact.
Likely exposure
Organizations using the identified AEM releases may be exposed, particularly where low-privileged users can reach affected functionality and persuade another user to open crafted content. The bundle does not identify vulnerable components, configurations, deployment patterns, or whether internet exposure is required.
Exploitation context
Exploitation requires user interaction: a victim must visit a specially crafted web page. The supplied CVSS vector also indicates low privileges are required. This CVE is not listed as KEV in the bundle, and no supplied source evidence establishes active exploitation or public exploit availability.
Researcher notes
The bundle’s narrative clearly names 6.5.24, FP11.7, and earlier, but its structured affected entry contains ambiguous values “0” and “11.8” with default status unaffected. Confirm exact applicability and fixed versions directly against APSB26-34. No vulnerable DOM source, sink, component, patch identifier, or exploitation telemetry is supplied.
Mitigation direction
Inventory Adobe Experience Manager deployments and record exact versions and installed feature packs.
Review Adobe advisory APSB26-34 for the vendor-designated fixed release and remediation instructions.
Upgrade affected deployments according to Adobe guidance using established change-control procedures.
Restrict unnecessary low-privileged access until remediation is completed.
Apply vendor-recommended compensating controls if immediate upgrading is not possible.
Validation and detection
Confirm each deployment’s AEM version and feature-pack level against Adobe advisory APSB26-34.
Verify the vendor-designated update installed successfully across all AEM nodes.
Run approved XSS-focused testing against affected functionality without using production user data.
Review browser and application security telemetry for suspicious script execution or crafted-link activity.
Retest after remediation and document any systems awaiting vendor guidance or maintenance windows.
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.