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

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

EUVD-2026-35711 MEDIUM

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

2026-06-09 psirt@adobe.com

GHSA-mfg4-6whx-795h

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:20 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) versions 6.5.24, LTS SP1, and 2026.04 and earlier enables a low-privileged authenticated attacker to inject persistent malicious JavaScript into vulnerable form fields. When any user browses to the affected page, the script executes in their browser under a changed scope (S:C), meaning the injected payload escapes the attacker's own session context and impacts other users - enabling session hijacking, credential harvesting, or unauthorized AEM actions on their behalf. No public exploit code or CISA KEV listing has been identified at time of analysis.

Technical ContextAI

Adobe Experience Manager is an enterprise content management platform built on Java, Apache Sling, and OSGi, widely deployed for web content authoring and digital asset management. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation - Stored XSS): user-supplied input submitted through form fields is persisted to the AEM repository without adequate sanitization, then later rendered in victim browsers without proper output encoding. The CVSS vector attribute S:C (Scope Changed) is technically significant here - the injected script executes in the browser security context of a different user than the attacker, not merely within the attacker's own session, which is the defining characteristic of stored XSS with cross-user impact. Affected versions span the 6.5.x legacy line through the current cloud-native AEM 2026.04 release, indicating the vulnerable form field handling is present across multiple product generations. No CPE strings were included in the source data; exact component-level identification should be cross-referenced against APSB26-56.

RemediationAI

Apply the vendor-released patch per Adobe Security Bulletin APSB26-56 at https://helpx.adobe.com/security/products/experience-manager/apsb26-56.html. An exact patched release version number was not extractable from the provided source data - consult APSB26-56 directly to identify the target upgrade version before deploying. As a compensating control prior to patching, restrict AEM content authoring and form field editing permissions to fully trusted, vetted users only, effectively eliminating the low-privileged attacker path (PR:L); note this may disrupt content workflows where external contributors require authoring access. Deploying a Web Application Firewall with XSS filtering rules in front of AEM can intercept common payload patterns but carries false-positive risk against legitimate rich-text content and should be validated in audit mode before enforcement. Configuring a strict Content Security Policy (CSP) header to block inline script execution provides meaningful defense-in-depth but requires review of existing AEM templates and third-party integrations to avoid breaking functionality before enforcement.