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

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

EUVD-2026-35712 MEDIUM

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

2026-06-09 psirt@adobe.com

GHSA-r3mc-6vjj-wp7r

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:10 vuln.today

DescriptionCVE.org

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

AnalysisAI

DOM-based Cross-Site Scripting in Adobe Experience Manager (AEM) versions 6.5.24, LTS SP1, and 2026.04 and earlier allows a low-privileged authenticated attacker to inject and execute malicious JavaScript within a victim's browser by manipulating the client-side DOM environment. The CVSS scope change (S:C) is the critical risk amplifier here: injected script executes outside the originating component's security boundary, potentially enabling session hijacking, credential theft, or privilege escalation against higher-privileged AEM users such as administrators. This CVE is not listed in the CISA KEV catalog and no public exploit code has been identified at time of analysis.

Technical ContextAI

Adobe Experience Manager is an enterprise content management platform built on Apache Sling and OSGi, widely deployed for web content authoring and digital asset management. DOM-based XSS (CWE-79, Improper Neutralization of Input During Web Page Generation) differs from reflected or stored XSS in that the malicious payload is processed entirely client-side - attacker-controlled data flows into a DOM sink such as innerHTML, document.write, or eval without server-side sanitization, making server-side WAF rules largely ineffective. The CVSS vector's S:C (Scope Changed) component indicates the injected script can access security contexts beyond the vulnerable AEM component itself, such as the hosting domain's cookies, local storage, or co-hosted applications sharing the same origin. The affected version range per ENISA EUVD-2026-35712 covers all AEM releases up to and including 2026.04, spanning both the legacy 6.5.x LTS line and the cloud-native continuous delivery track.

RemediationAI

The primary remediation is to apply the patch documented in Adobe security advisory APSB26-56 at https://helpx.adobe.com/security/products/experience-manager/apsb26-56.html. The exact patched release number (specific Service Pack or Cloud Service release) is not independently confirmable from the available input data - consult the advisory directly to identify the minimum fixed version for your deployment track (6.5.x LTS or AEM as a Cloud Service). As a compensating control prior to patching, restrict AEM Author environment access to trusted internal networks or VPN-only ingress; this prevents external attackers from delivering crafted URLs to privileged users and is the single highest-impact workaround available, though it does not address insider threat scenarios. Enabling a strict Content Security Policy (CSP) on AEM Author and Publish tiers can reduce DOM XSS impact by blocking inline script execution, but CSP configuration in AEM is non-trivial and requires regression testing against authoring UI components before deployment. Web Application Firewall rules offer limited protection for DOM-based XSS since payload processing is client-side, but may catch known payload patterns in URL parameters as a defense-in-depth measure.