CVE-2025-34509: Sitecore XM and XP Hardcoded Credentials

Published Jun 17, 2025
·
Updated

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.

Affected Software

7 affected components
Sitecore Experience Manager>=10.1<=10.1.4, =10.2, >=10.3<10.3.3, >=10.4<10.4.1
Sitecore Experience Platform>=10.1<=10.1.4, =10.2, >=10.3<10.3.3, >=10.4<10.4.1
Sitecore Experience Commerce>=9.0<=10.4
Sitecore Experience Manager>=9.0<=10.4
Sitecore Experience Platform>=9.0<10.4
Sitecore Experience Platform=10.4
Sitecore Managed Cloud

Remediation

Information

Update to patched versions.

Event History

Jun 17, 2025
CVE Published
via MITRE·06:20 PM
Data Sourced
via MITRE·06:20 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·07:15 PM
DescriptionSeverityWeaknessAffected Software
Jul 16, 57959
Event
via MITRE·06:48 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-34509?

CVE-2025-34509 is considered a critical vulnerability due to its exploitation potential by unauthenticated remote attackers.

2

How do I fix CVE-2025-34509?

To fix CVE-2025-34509, upgrade to the latest version of Sitecore Experience Manager or Experience Platform that does not contain the hardcoded user account.

3

What versions are affected by CVE-2025-34509?

CVE-2025-34509 affects Sitecore Experience Manager and Experience Platform versions 10.1 to 10.1.4, 10.2, 10.3 to 10.3.3, and 10.4 to 10.4.1.

4

What impact does CVE-2025-34509 have on my system?

CVE-2025-34509 allows unauthenticated attackers to gain unauthorized access, potentially compromising sensitive data.

5

Is there a workaround for CVE-2025-34509?

There is no recommended workaround for CVE-2025-34509; the best course of action is to apply the necessary updates or patches.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203