cve.bz

CVE-2025-24011 umbraco umbraco cms: Observable Discrepancy

5.3 mediumEPSS 1.6%Fix available

Medium (5.3) in umbraco umbraco cms. EPSS 1.6% estimated probability of exploitation activity in the next 30 days. Fixed in Umbraco.Cms 14.3.2, 15.1.2.

On this page
Umbraco is a free and open source .NET content management system. Starting in version 14.0.0 and prior to versions 14.3.2 and 15.1.2, it's possible to determine whether an account exists based on an analysis of response codes and timing of Umbraco management API responses. Versions 14.3.2 and 15.1.2 contain a patch. No known workarounds are available.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
1.6% (unchanged from 1.6% a week ago; 1.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 77th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-01-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-203 Observable Discrepancy
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-24011 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-24011?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-24011?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-24011 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
umbraco:umbraco_cmsfrom 14.0.0 before 14.3.2
umbraco:umbraco_cmsfrom 15.0.0 before 15.1.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-hmg4-wwm5-p999NuGetUmbraco.Cms>=14.0.0 <14.3.214.3.2
GHSA-hmg4-wwm5-p999NuGetUmbraco.Cms>=15.0.0 <15.1.215.1.2

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

  • CAPEC-189 Black Box Reverse Engineering Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON