VulnerabilityPublished 17 Jun 2025Updated 26 Feb 2026

CVE-2025-34509: Sitecore Experience Manager · Use of Hard-coded Credentials

Affects Sitecore Experience ManagerSource CVE Database V5

Not known to be exploited · public detection template (Nuclei) · 55% EPSS · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 55.8% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Jun 2025
Detectable: evidence found.
nuclei template: Sitecore Experience Manager (XM) and Experience Platform (XP) - Hardcoded Credentials
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
NuGetSitecore/experiencemanager`pkg:nuget/Sitecore/experiencemanager`Other threats	Affected =10.1 =10.3 =10.4	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediately verify if your Sitecore Experience Manager or Experience Platform deployment is running any affected versions (10.1 to 10.4.1).
Monitor Sitecore’s official channels for patches or security advisories addressing CVE-2025-34509 and apply updates as soon as they are released.
If patches are not yet available, implement network-level access controls to restrict HTTP access to Sitecore administrative APIs to trusted IP addresses only, using firewalls or web application firewalls (WAFs).
Conduct a thorough audit of user accounts and credentials within Sitecore to identify and disable any hardcoded or default accounts if possible.
Enable detailed logging and monitoring on Sitecore servers to detect unusual access patterns or unauthorized API calls, integrating with SIEM solutions for real-time alerting.
Employ network segmentation to isolate Sitecore servers from general user networks, minimizing exposure.
Review and enforce strong authentication and authorization policies for all administrative interfaces beyond the vulnerable API endpoints.
Educate IT and security teams about the risks of hardcoded credentials and incorporate secure coding practices in development and deployment processes.
Consider deploying runtime application self-protection (RASP) or endpoint detection and response (EDR) tools to detect and block exploitation attempts.
Prepare an incident response plan specifically for Sitecore-related breaches, including containment and recovery procedures.

Description

Sitecore Experience Manager (XM) and Experience Platform (XP) versions 10.1 to 10.1.4 rev.011974 PRE, all versions of 10.2, 10.3 to 10.3.3 rev.011967 PRE, and 10.4 to 10.4.1 rev.011941 PRE contain a hardcoded user account. Unauthenticated and remote attackers can use this account to access administrative API over HTTP.

Impact

The primary impact of CVE-2025-34509 is unauthorized access to administrative APIs of Sitecore Experience Manager and Experience Platform, which can lead to exposure of sensitive data managed by these systems. Since the vulnerability allows unauthenticated remote access, attackers can potentially enumerate, extract, or manipulate administrative data without detection. While the CVSS score indicates no direct integrity or availability impact, the confidentiality breach alone can have severe consequences, including data leaks, intellectual property theft, or preparation for further attacks such as privilege escalation or lateral movement within an organization’s network. Organizations relying on Sitecore for content management, digital marketing, or customer experience platforms face reputational damage, compliance violations, and operational disruptions if exploited. The vulnerability affects multiple recent versions, increasing the scope of affected systems globally. Given Sitecore’s widespread use in enterprise environments, especially in sectors like retail, finance, healthcare, and government, the risk of targeted attacks is significant. The lack of authentication and user interaction requirements lowers the barrier for exploitation, making automated scanning and exploitation feasible for attackers. The absence of known exploits in the wild currently provides a window for proactive mitigation, but the threat landscape could evolve rapidly once exploit code becomes available.

CWE-798Use of Hard-coded Credentials (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product contains hard-coded credentials, such as a password or cryptographic key.
Architecture and Design
For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320).
Architecture and Design
For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password or key.
Architecture and Design
If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
OWASP Cheat Sheets
Key Management (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.4 (opens in a new tab)
V6.4.1 (opens in a new tab)
V3.5.2 (opens in a new tab)
Attack patterns
Read Sensitive Constants Within an Executable (opens in a new tab)
Try Common or Default Usernames and Passwords (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 01:43 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-798

Technical details

References

Community reviews

Related threats