How severe is CVE-2025-34139?

CVE-2025-34139 has a CVSS 4.0 base score of 8.7, rated high severity.

Is CVE-2025-34139 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (37th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-34139?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-34139 have an EU (EUVD) identifier?

Yes. CVE-2025-34139 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-22720.

When was CVE-2025-34139 published?

CVE-2025-34139 was published on 2025-07-25 and last updated on 2026-06-17.

CVE-2025-34139

CVE-2025-34139 is a high-severity vulnerability with a CVSS 4.0 base score of 8.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-522.

Key facts

Severity: High (CVSS 4.0 base score 8.7)
EPSS exploit prediction: 0% (37th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-22720
Weakness: CWE-522
Published: 2025-07-25
Last modified: 2026-06-17

Description

A vulnerability exists in Sitecore Experience Manager (XM), Experience Platform (XP), Experience Commerce (XC), and Managed Cloud that could allow an unauthenticated attacker to read arbitrary files. This vulnerability affects all Experience Platform topologies (XM, XP, XC) from 8.0 Initial Release through 10.4 Initial Release and later. This issue affects Content Management (CM) and standalone instances. PaaS and containerized solutions are also affected.

Frequently asked questions

What is CVE-2025-34139?: A vulnerability exists in Sitecore Experience Manager (XM), Experience Platform (XP), Experience Commerce (XC), and Managed Cloud that could allow an unauthenticated attacker to read arbitrary files. This vulnerability affects all Experience Platform topologies (XM, XP, XC) from 8.0 Initial Release through 10.4 Initial Release and later. This issue affects Content Management (CM) and standalone instances. PaaS and containerized solutions are also affected.
How severe is CVE-2025-34139?: CVE-2025-34139 has a CVSS 4.0 base score of 8.7, rated high severity.
Is CVE-2025-34139 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (37th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-34139?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-34139 have an EU (EUVD) identifier?: Yes. CVE-2025-34139 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-22720.
When was CVE-2025-34139 published?: CVE-2025-34139 was published on 2025-07-25 and last updated on 2026-06-17.

References

Other CWE-522 (Insufficiently Protected Credentials) vulnerabilities

CVE-2026-7312 — Critical (CVSS 10.0): CWE‑522: Insufficiently Protected Credentials in web services in Progress Sitefinity version from 14.0.7700 to…
CVE-2026-29128 — Critical (CVSS 10.0): IDC SFX2100 Satellite Receiver firmware ships with multiple daemon configuration files for routing components (e.g.,…
CVE-2025-54863 — Critical (CVSS 10.0): Radiometrics VizAir is vulnerable to exposure of the system's REST API key through a publicly accessible configuration…
CVE-2024-12799 — Critical (CVSS 10.0): Insufficiently Protected Credentials vulnerability in OpenText Identity Manager Advanced Edition on Windows, Linux, 64…
CVE-2024-51545 — Critical (CVSS 10.0): Username Enumeration vulnerabilities allow access to application level username add, delete, modify and list…
CVE-2023-1778 — Critical (CVSS 10.0): This vulnerability exists in GajShield Data Security Firewall firmware versions prior to v4.28 (except v4.21) due to…

Browse all CWE-522 (Insufficiently Protected Credentials) vulnerabilities →