Skip to content

GHSA-pgvc-6h2p-q4f6 CVE-2025-49147

Umbraco CMS disclosure of configured password requirements

Medium NuGet
Severity
5.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.34%
Chance of exploitation in the next 30 days. Higher than 27.81% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-497 Exposure of Sensitive System Information to an Unauthorized Control Sphere
Fix
10.8.11
Upgrade Umbraco.Cms to this version or later

Description

Impact

Via a request to an anonymously authenticated endpoint it's possible to retrieve information about the configured password requirements. The information available is limited but would perhaps give some additional detail useful for someone attempting to brute force derive a user's password.

The vulnerability can be found in the supported Umbraco versions 10 and 13. It was not exposed in Umbraco 7 or 8, nor in 14 or higher versions.

Patches

Patched in 10.8.11 and 13.9.2

Affected versions

NuGet

PackageVulnerableFixed in
Umbraco.Cms
>= 10.0.0, < 10.8.11
10.8.11
Umbraco.Cms
>= 13.0.0, < 13.9.2
13.9.2

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 → 10.8.11

dotnet
dotnet add package Umbraco.Cms --version 10.8.11

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-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere

The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.

How to prevent it
  • Architecture and Design, Implementation: Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user. All error message text should be HTML entity encoded before being written to the log file to protect against potential cross-site scripting attacks against the viewer of the logs

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