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

CVE-2026-47973 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-47973

EUVD-2026-35718 MEDIUM

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

2026-06-09 psirt@adobe.com

GHSA-3w6w-3mq9-wprw

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 Cross-Site Scripting in Adobe Experience Manager (AEM) 2026.04 and earlier enables a low-privileged authenticated attacker to inject persistent malicious JavaScript into vulnerable form fields. When any user - including administrators - browses to a page containing the injected content, the script executes in their browser under a changed security scope (S:C), potentially compromising confidentiality and integrity of the victim's session. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog; however, AEM's widespread enterprise deployment and the low barrier of entry (low-privilege account only) make this a meaningful risk in environments where untrusted or lightly vetted users have authoring or form-editing access.

Technical ContextAI

Adobe Experience Manager is an enterprise-grade content management and digital experience platform widely deployed in large organizations for web content authoring and delivery. The vulnerability is rooted in CWE-79 (Improper Neutralization of Input During Web Page Generation - Stored XSS), meaning user-supplied input written to AEM form fields is persisted in the application's data store and subsequently rendered in browser contexts without adequate output encoding or sanitization. The CVSS vector AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N indicates network-accessible exploitation with low attack complexity, low privilege, but requiring victim interaction; the changed scope (S:C) is significant - it means the injected script can affect browser resources outside the vulnerable AEM component's own security context, such as cookies or content from other origins depending on same-site policies. Affected versions per ENISA EUVD-2026-35718 span all AEM releases through 2026.04, covering both the legacy 6.5.x LTS line and the cloud-native AEM as a Cloud Service track.

RemediationAI

The primary remediation is to apply the patch referenced in Adobe Security Bulletin APSB26-56, available at https://helpx.adobe.com/security/products/experience-manager/apsb26-56.html. Patch available per vendor advisory; an exact patched release version was not independently confirmed in the available intelligence data - consult the APSB26-56 bulletin directly for the precise fixed build for your AEM track (6.5.x LTS or AEM as a Cloud Service). While awaiting patching, the most effective compensating control is to restrict the low-privileged authoring and form-editing roles to fully trusted internal users only, removing or suspending external contributors and third-party editors, since the vulnerability requires an authenticated low-privileged account. Additionally, enabling a strict Content Security Policy (CSP) on AEM delivery tiers can limit the impact of any executed XSS payload by restricting inline script execution and cross-origin data exfiltration, though CSP does not eliminate the underlying vulnerability. Web Application Firewall (WAF) rules targeting stored XSS patterns in AEM form submissions can provide a partial detection and blocking layer, but these have known bypass vectors and should not be treated as equivalent to patching.