Skip to main content

Adobe Experience Manager CVE-2025-64546

MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2025-12-10 psirt@adobe.com
5.4
CVSS 3.1 · Vendor: adobe
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privileged AEM user
  2. Delivery
    Inject script into vulnerable form field
  3. Exploit
    Payload stored in AEM content
  4. Execution
    Victim browses affected page
  5. Persist
    Malicious JS executes in victim browser
  6. Impact
    Session/context compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated low-privileged account on the Adobe Experience Manager instance (PR:L) with the ability to submit content into affected form fields, plus a victim who subsequently browses to the page rendering that field (UI:R). Affected deployments are AEM 6.5.23 and earlier, including AEM Cloud Service and the 6.5 LTS build per the CPE strings. Exploitation is limited by these two gates - attacker must already hold form-authoring/contributor access and the injected page must be viewed by another user - and impact is bounded to Low confidentiality and Low integrity in the victim's browser (client-side script execution, not server-side RCE).

Impact

This is a genuine but low-priority issue. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, base 5.4) is double-gated: it requires an authenticated low-privileged attacker (PR:L) to inject the payload AND a victim to browse to the affected page (UI:R), with only Low confidentiality and integrity impact and no availability impact. EPSS is very low at 0.20% (9th percentile), consistent with a stored XSS in an authoring/enterprise CMS rather than a mass-exploited flaw. There is no CISA KEV listing and no public exploit identified at time of analysis - signals align (low EPSS, no KEV, no POC), so nothing is conflicting here. This is a real-but-modest finding: standard XSS remediation priority, not an emergency. The stored nature (payload persists in form fields, S:C scope change into the victim browser context) makes it more durable than reflected XSS, which is the one factor that argues against fully deprioritizing it.

Exploit ScenarioDerived

A low-privileged AEM user (e.g. a form author or content contributor) injects a malicious JavaScript payload into a vulnerable form field. The script is stored and later executes in the browser of any victim - such as an administrator or reviewer - who navigates to the page rendering that field, enabling session token theft or actions in the victim's authenticated context. No public exploit code is identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 25, 2026

Stored cross-site scripting in Adobe Experience Manager (AEM) 6.5.23 and earlier lets an authenticated low-privileged user persist malicious JavaScript into vulnerable form fields, which then executes in the browser of any victim who later views the affected page. Exploitation requires two gates: an attacker account with contributor/form-authoring privileges that can submit content into the vulnerable field (CVSS PR:L), and a second user who browses to the page rendering that field (UI:R); the resulting impact is limited to Low confidentiality and Low integrity in the victim's browser via changed scope, with no server-side code execution. At the time of analysis there is no confirmed active exploitation (not in CISA KEV), no public exploit code identified, and the EPSS score is very low at 0.20% (9th percentile), making this a genuine but low-priority issue.

RemediationAI

The primary fix is to upgrade to the patched Adobe Experience Manager release identified in Adobe security bulletin APSB25-115 (https://helpx.adobe.com/security/products/experience-manager/apsb25-115.html), which is the vendor advisory addressing this issue for the AEM 6.5 and 6.5 LTS tracks; AEM Cloud Service instances are patched automatically by Adobe and should be verified against the bulletin rather than patched manually. Because the provided data does not name an exact patched build number, confirm the specific fixed version from the advisory before scheduling the upgrade. Where an immediate upgrade is not possible, restrict the form-authoring and content-contributor permissions that the PR:L vector relies on so that only trusted accounts can submit into form fields - this meaningfully reduces the attack surface but can break legitimate authoring workflows for lower-tier contributors. Additionally, enforce a strict Content-Security-Policy on AEM author and publish tiers to block inline script execution (trade-off: AEM components and third-party widgets that rely on inline JavaScript may stop rendering and require nonce/hash configuration), and deploy WAF or reverse-proxy rules that strip script tags and event-handler attributes from form submissions - with the caveat that pattern-based filtering can be bypassed by encoded payloads and may generate false positives on legitimate rich content. Reviewing stored form data for pre-existing injected payloads is also advisable, since remediating only the software leaves previously persisted scripts in the repository.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This is a classic stored (persistent) cross-site scripting flaw, classed as CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). The root cause is insufficient output encoding or input sanitization of user-supplied content stored by AEM's form components, so markup and script payloads submitted into form fields are persisted and later rendered verbatim inside a page served to other users. Per the CPE strings the affected surface spans the core AEM 6.5 product line (cpe:2.3:a:adobe:experience_manager, including the 6.5 LTS build) and the AEM Cloud Service (aem_cloud_service) edition, meaning both on-premise/managed 6.5 deployments and hosted cloud instances share the vulnerable code path. Because execution happens in the victim's browser session rather than on the server, the CVSS vector scores Scope as Changed (S:C) but Confidentiality and Integrity as Low, with Availability unaffected (A:N). The attack is network-reachable (AV:N) and requires no special complexity (AC:L), but the PR:L rating confirms the attacker must already hold an authenticated AEM account with enough privilege to author or submit form content, while the UI:R rating confirms a separate victim must load the poisoned page.

Know when Experience Manager gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

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
vuln.today AI 5.4 MEDIUM

Network-reachable stored XSS needing a low-privileged author account (PR:L) and victim page view (UI:R); script crosses into browser context (S:C) with limited C/I impact and no availability effect.

3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (adobe).

CVSS VectorVendor: adobe

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

Adobe Experience Manager versions 6.5.23 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.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Medium
widely-used enterprise CMS but authoring-tier flaw limits exposed surface
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

27
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +27
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

Affected Products (CPE)CVE.org

cpe:2.3:a:adobe:experience_manager:*:*:*:*:-:*:*:*
cpe:2.3:a:adobe:experience_manager:*:*:*:*:aem_cloud_service:*:*:*
cpe:2.3:a:adobe:experience_manager:6.5:-:*:*:lts:*:*:*
CVE-2025-34510 HIGH POC
8.8 Jun 17

Sitecore Experience Manager, Platform, and Commerce versions 9.0 through 10.4 contain a Zip Slip vulnerability that allo

CVE-2025-34511 HIGH POC
8.8 Jun 17

Sitecore PowerShell Extensions through version 7.0 allows authenticated users to upload arbitrary files including ASPX w

CVE-2016-0957 HIGH POC
7.5 Feb 10

Dispatcher before 4.1.5 in Adobe Experience Manager 5.6.1, 6.0.0, and 6.1.0 does not properly implement a URL filter, wh

CVE-2025-53690 CRITICAL POC
9.0 Sep 03

Sitecore Experience Manager/Platform through version 9.0 contains a deserialization vulnerability enabling code injectio

CVE-2025-49533 CRITICAL POC
9.8 Jul 08

Adobe Experience Manager versions 6.5.23.0 and earlier contain a deserialization of untrusted data vulnerability that al

CVE-2025-34509 HIGH POC
7.5 Jun 17

Sitecore Experience Manager (XM) and Experience Platform (XP) versions 10.1 through 10.4.1 contain a hardcoded administr

CVE-2016-0956 HIGH POC
7.5 Feb 10

The Servlets Post component 2.3.6 in Apache Sling, as used in Adobe Experience Manager 5.6.1, 6.0.0, and 6.1.0, allows r

CVE-2025-53693 CRITICAL POC
9.8 Sep 03

Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in Sitecore Sitecore Ex

CVE-2023-35813 CRITICAL POC
9.8 Jun 17

Multiple Sitecore products allow remote code execution. Rated critical severity (CVSS 9.8), this vulnerability is remote

CVE-2025-53691 HIGH POC
8.8 Sep 03

Deserialization of Untrusted Data vulnerability in Sitecore Experience Manager (XM), Sitecore Experience Platform (XP) a

CVE-2017-3108 CRITICAL
9.8 Aug 11

Adobe Experience Manager 6.2 and earlier has a malicious file execution vulnerability. Rated critical severity (CVSS 9.8

CVE-2025-54249 MEDIUM POC
6.5 Sep 09

Adobe Experience Manager versions 6.5.23.0 and earlier are affected by a Server-Side Request Forgery (SSRF) vulnerabilit

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy