Skip to content
Fencer Vulns
medium 5.3

CVE-2025-46736 json

Umbraco Makes User Enumeration Feasible Based on Timing of Login Response

published 2025-05-06 18 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-13623 , GHSA-4g8m-5mj5-c8xg

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 33%
public exploits
0
none known

Summary

Umbraco is a free and open source .NET content management system. Prior to versions 10.8.10 and 13.8.1, based on an analysis of the timing of post login API responses, it's possible to determine whether an account exists. The issue is patched in versions 10.8.10 and 13.8.1. No known workarounds are available.

Patch / fix

  • nuget Umbraco.Cms 10.8.10, 13.8.1
  • umbraco umbraco_cms 10.8.10, 13.8.1

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
nuget Umbraco.Cms
>=11.0.0-rc1, <13.8.1
<10.8.10
13.8.1
10.8.10

Affected products

  • umbraco Umbraco-CMS

Classification

Weakness
  • CWE-204 Observable Response Discrepancy

References

Sources

Fencer Vulns 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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.