Loading vulnerability…
CVE-2025-24011 is a user enumeration vulnerability in Umbraco, the open source .NET content management system. In Umbraco versions starting at 14.0.0 and prior to 14.3.2 and 15.1.2, the management API returns distinguishable response codes and exhibits timing differences that allow an attacker to infer whether a given account exists. The issue arises from observable discrepancies in API behavior during account-related requests, enabling account existence to be determined without direct disclosure of user data.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept exploit for CVE-2025-24011, targeting Umbraco CMS (tested on versions 15.1.1 and 13.7.2 on Ubuntu 24.04.2 LTS). The exploit is implemented in a single Python script (poc.py) and is accompanied by a README.md with usage instructions and lab setup guidance. The exploit leverages a timing side-channel in the Umbraco login API endpoints to enumerate valid usernames (email addresses) by measuring the response time for login attempts with random passwords. The script first builds a timing model by sending login requests with non-existent usernames, then tests a supplied list of usernames to identify which ones exist based on anomalous response times. The endpoints targeted are the Umbraco login APIs, with the specific path depending on the Umbraco version. No actual authentication is bypassed, but the script can reveal which usernames are valid, which may aid further attacks. The repository is a standalone POC and not part of a larger framework.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.