CVE-2025-46736: Umbraco Makes User Enumeration Feasible Based on Timing of Login Response

Published May 6, 2025
·
Updated

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.

Other sources

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.

MITRE

Affected Software

4 affected componentsFixes available
nuget/Umbraco.Cms<10.8.10
10.8.10
nuget/Umbraco.Cms>=11.0.0-rc1<13.8.1
13.8.1
Umbraco Umbraco CMS<10.8.10
Umbraco Umbraco CMS>=10.9.0<13.8.1

Event History

May 6, 2025
Advisory Published
via GitHub·04:38 PM
CVE Published
via MITRE·05:08 PM
Data Sourced
via MITRE·05:08 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
RemedyAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-46736?

CVE-2025-46736 is considered a moderate severity vulnerability due to its potential for account enumeration.

2

How do I fix CVE-2025-46736?

To address CVE-2025-46736, upgrade Umbraco.Cms to version 10.8.10 or 13.8.1 or later.

3

What does CVE-2025-46736 impact?

CVE-2025-46736 impacts Umbraco.Cms versions prior to 10.8.10 and 13.8.1.

4

Are there any workarounds for CVE-2025-46736?

There are no workarounds available for CVE-2025-46736.

5

How can CVE-2025-46736 affect user accounts?

CVE-2025-46736 allows an attacker to determine if a user account exists based on the timing of post login API responses.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203