Skip to content

GHSA-4g8m-5mj5-c8xg CVE-2025-46736

Umbraco Makes User Enumeration Feasible Based on Timing of Login Response

Medium NuGet
Severity
5.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.38%
Chance of exploitation in the next 30 days. Higher than 32.22% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-204 Observable Response Discrepancy
Fix
13.8.1
Upgrade Umbraco.Cms to this version or later

Description

Impact

Based on an analysis of the timing of post login API responses, it's possible to determine whether an account exists.

Patches

Patched in 10.8.10 and 13.8.1.

Workarounds

None available.

Affected versions

NuGet

PackageVulnerableFixed in
Umbraco.Cms
>= 11.0.0-rc1, < 13.8.1
13.8.1
Umbraco.Cms
< 10.8.10
10.8.10

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

Umbraco.Cms NuGet → 13.8.1

dotnet
dotnet add package Umbraco.Cms --version 13.8.1

Severity breakdown

CVSS 3.1 5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-204: Observable Response Discrepancy

The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
  • Implementation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-wr57-hqmp-fgvh
Umbraco: Delivery API leaks protected (Public Access) content through Content Picker / Multi-Node Tree Picker expansion
High Also affects Umbraco.Cms
GHSA-vr9v-27gg-qgx4
Umbraco.Cms: XSS/HTML Injection in Umbraco Backoffice confirmation dialog
Medium Also affects Umbraco.Cms
GHSA-2qjj-h6wp-c7h7
Umbraco.Cms: Open Redirect Vulnerability in Surface Controllers
Medium Also affects Umbraco.Cms
GHSA-rhcg-3h8r-v6vp
Umbraco Affected by Vertical Privilege Escalation via Missing Authorization Checks
High Also affects Umbraco.Cms
GHSA-vrqc-59mw-qqg7
Umbraco has Stored XSS in UFM Rendering Pipeline via Permissive DOMPurify Attribute Filtering
Medium Also affects Umbraco.Cms
GHSA-fpvf-fvp5-996r
Umbraco Backoffice API Allows Unauthorized Modification of Domain Data
Medium Also affects Umbraco.Cms
GHSA-54mj-vcvj-q3v5
Umbraco CMS has an arbitrary file upload vulnerability
Critical Also affects Umbraco.Cms
GHSA-hfv2-pf68-m33x
Umbraco Vulnerable to Improper File Access and Credential Exposure in Dictionary Import Functionality
Medium Also affects Umbraco.Cms
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor