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

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

EUVD-2026-35721 MEDIUM

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

2026-06-09 psirt@adobe.com

GHSA-8r5c-rrrq-8gv3

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:30 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 (versions up to 6.5.24, LTS SP1, and 2026.04) allows a low-privileged authenticated attacker to inject persistent malicious JavaScript into vulnerable form fields within the platform. When a higher-privileged user - such as an administrator or content editor - subsequently browses to a page containing the poisoned field, the injected script executes in their browser, enabling session hijacking, credential theft, or unauthorized actions on their behalf. No public exploit has been identified at time of analysis and the vulnerability is not listed in the CISA KEV catalog; Adobe has published advisory APSB26-56 to address this issue.

Technical ContextAI

Adobe Experience Manager (AEM) is a widely deployed enterprise content management platform used for web content authoring, digital asset management, and omnichannel publishing. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation - Stored/Persistent XSS): user-supplied input accepted through form fields is written to the AEM repository without adequate sanitization or output encoding, and is later rendered verbatim in a victim's browser. The CVSS Scope:Changed (S:C) attribute is significant here - it confirms that script execution crosses the boundary of the vulnerable AEM component and operates within the victim's browser session, potentially affecting resources or sessions outside AEM's direct authorization scope. Affected product lines include the 6.5.x on-premise branch (up to and including 6.5.24), the Long-Term Support SP1 release, and the Adobe Experience Manager as a Cloud Service rolling track through the 2026.04 release, as confirmed by EUVD-2026-35721 coverage of Adobe Experience Manager versions 0 through 2026.04.

RemediationAI

Consult Adobe security advisory APSB26-56 at https://helpx.adobe.com/security/products/experience-manager/apsb26-56.html for exact patched release versions and update procedures specific to your AEM deployment track (6.5.x Service Pack, LTS, or Cloud Service). The patched version number is not independently confirmed in the available intelligence - do not upgrade based on this analysis alone; verify against the APSB26-56 advisory before applying changes. As an immediate compensating control, restrict write access to HTML-capable and rich-text form fields to the minimum set of trusted roles required for business operations; this reduces the attack surface without disabling AEM authoring entirely, though it may impact content publishing workflows. Enforce a strong Content Security Policy (CSP) header - specifically a policy that disallows inline script execution - via AEM's Dispatcher or CDN layer; note this may break legacy AEM UI components that rely on inline scripts and requires testing before broad deployment. Additionally, validate that AEM's built-in XSS Protection API (com.adobe.granite.xss.XSSAPI) is enforced at all custom component output paths, particularly in form renderers.