Skip to content
Fencer Intel
high 7.5

CVE-2025-34509 in the critical feed json

Sitecore XM and XP Hardcoded Credentials

published last yr. modified 11d ago also EUVD-2025-18524

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
55.9%
EPSS 55.9% chance of exploitation in 30 days, percentile 99%
public exploits
0
none known, plus a Nuclei check

Summary

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.

Patch / fix

  • Sitecore Experience Manager 10.1.4 rev. 011974 PRE, 10.3, 10.3.3 rev. 011967 PRE, 10.4.1 rev. 011941 PRE
  • Sitecore Experience Platform 10.1.4 rev. 011974 PRE, 10.3, 10.3.3 rev. 011967 PRE, 10.4.1 rev. 011941 PRE

Is CVE-2025-34509 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

55.87% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template Sitecore Experience Manager (XM) and Experience Platform (XP) - Hardcoded Credentials nuclei detection template
  • labs.watchtowr.com https://labs.watchtowr.com/is-b-for-backdoor-pre-auth-rce-chain-in-sitecore-experience-platform/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

  • Sitecore Experience Manager
  • Sitecore Experience Platform

Classification

Weakness
  • CWE-798 Use of Hard-coded Credentials

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.