What is the CVSS score of CVE-2026-47972?

CVE-2026-47972 has a CVSS 3.1 base score of 5.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

Adobe Experience Manager CVE-2026-47972

EUVD-2026-35622 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-06-09 psirt@adobe.com

GHSA-mq2q-567c-v6rg

XSS Adobe Experience Manager

5.4

CVSS 3.1 · Vendor: adobe

Severity by source

Vendor (adobe) PRIMARY

5.4 MEDIUM

AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Primary rating from Vendor (adobe) · only source for this CVE.

CVSS VectorVendor: adobe

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 09, 2026 - 19:22 vuln.today

DescriptionCVE.org

Adobe Experience Manager versions 6.5.24, LTS SP1, 2026.04 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. Scope is changed.

AnalysisAI

Stored XSS in Adobe Experience Manager (versions 6.5.24, LTS SP1, and 2026.04 and earlier) allows a low-privileged authenticated attacker to inject persistent malicious JavaScript into vulnerable form fields within the platform's content authoring interface. When a victim - typically an administrator or higher-privileged user - browses the page containing the injected field, the script executes in their browser, enabling session hijacking, credential theft, or unauthorized privileged actions. No public exploit has been identified at time of analysis and this vulnerability is not listed in CISA KEV; however, the changed scope (S:C) in the CVSS vector elevates the effective impact beyond the originating component, making this a meaningful risk in environments with untrusted low-privilege authors.

Technical ContextAI

Adobe Experience Manager (AEM) is an enterprise content management and digital asset management platform built on Apache Sling and OSGi, used extensively for web content authoring in large organizations. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation - Stored XSS): user-supplied input submitted via form fields is persisted to the AEM content repository (JCR) without adequate sanitization or output encoding, and is later rendered as raw HTML in victim browsers. The CVSS:3.1 vector AV:N/AC:L/PR:L/UI:R/S:C encodes several important technical facts: the attack is network-exploitable with low complexity; it requires a low-privileged AEM account (PR:L, consistent with standard author or contributor roles); it demands that a second user visit the affected page (UI:R); and critically, the scope is changed (S:C), meaning the injected script executes within the victim's browser security context rather than being confined to the AEM application's own origin - crossing a trust boundary. Affected versions span both the AEM Classic release train (through 6.5.24 and LTS SP1) and AEM as a Cloud Service (through 2026.04), as confirmed by ENISA EUVD-2026-35622.

RemediationAI

Apply the vendor-released patches documented in Adobe Security Bulletin APSB26-56 at https://helpx.adobe.com/security/products/experience-manager/apsb26-56.html. Adobe has confirmed patch availability for both the AEM 6.5 Classic release train (targeting 6.5.24 and LTS SP1) and AEM as a Cloud Service (2026.04 and earlier); exact patched build numbers must be verified directly from the advisory, as they are not enumerated in the available intelligence. As a compensating control pending patching, restrict content authoring and form-editing permissions to trusted, fully-vetted internal users only - removing write access from low-privileged or external contributor accounts eliminates the PR:L attack surface entirely. Additionally, implementing a strict Content Security Policy (CSP) header with a script-src allowlist on AEM publish and author instances can limit the impact of any injected scripts by preventing unauthorized script execution; note that AEM's authoring interface uses inline scripts extensively, so CSP deployment must be tested thoroughly in a staging environment to avoid breaking the authoring UI. AEM's built-in AntiSamy or HTML Library Manager (HtmlLM) output encoding should be verified as enabled for all affected field renderers.