Sitecore Experience Manager/Experience Platform 10.1.4/10.3.3/10.4.1 Administrative API hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Sitecore Experience Manager and Experience Platform 10.1.4/10.3.3/10.4.1. It has been declared as critical. This impacts an unknown function of the component Administrative API. Such manipulation leads to hard-coded credentials. This vulnerability is traded as CVE-2025-34509. The attack may be launched remotely. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Sitecore Experience Manager and Experience Platform 10.1.4/10.3.3/10.4.1. It has been rated as critical. Affected by this issue is some unknown processing of the component Administrative API. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. Using CWE to declare the problem leads to CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. Impacted is confidentiality, integrity, and availability. CVE summarizes:
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.
The weakness was shared by Piotr Bazydlo. The advisory is available at labs.watchtowr.com. This vulnerability is handled as CVE-2025-34509 since 04/15/2025. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1110.001 by the MITRE ATT&CK project.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-18524). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔒
CNA Base Score: 7.5
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Timeline
04/15/2025 CVE reserved06/17/2025 Advisory disclosed
06/17/2025 VulDB entry created
12/27/2025 VulDB entry last update
Sources
Advisory: labs.watchtowr.comResearcher: Piotr Bazydlo
Status: Confirmed
CVE: CVE-2025-34509 (🔒)
GCVE (CVE): GCVE-0-2025-34509
GCVE (VulDB): GCVE-100-312794
EUVD: 🔒
Entry
Created: 06/17/2025 21:03Updated: 12/27/2025 18:42
Changes: 06/17/2025 21:03 (64), 06/17/2025 22:07 (1), 07/22/2025 18:36 (5), 09/08/2025 22:24 (9), 12/27/2025 18:42 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.