CVE-2025-66625: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in umbraco Umbraco-CMS
Umbraco is an ASP.NET CMS. Due to unsafe handling and deletion of temporary files in versions 10.0.0 through 13.12.0, during the dictionary upload process an attacker with access to the backoffice can trigger predictable requests to temporary file paths. The application’s error responses (HTTP 500 when a file exists, 404 when it does not) allow the attacker to enumerate the existence of arbitrary files on the server’s filesystem. This vulnerability does not allow reading or writing file contents. In certain configurations, incomplete clean-up of temporary upload files may additionally expose the NTLM hash of the Windows account running the Umbraco application. This issue is fixed in version 13.12.1.
AI Analysis
Technical Summary
Umbraco CMS, an ASP.NET-based content management system, suffers from a vulnerability (CVE-2025-66625) affecting versions 10.0.0 up to but not including 13.12.1. The root cause lies in the unsafe handling and deletion of temporary files generated during the dictionary upload process. An attacker with legitimate backoffice credentials can send crafted requests targeting predictable temporary file paths. The server's error responses differ based on whether the file exists: HTTP 500 if the file is present and HTTP 404 if absent. This discrepancy allows the attacker to enumerate arbitrary files on the server filesystem, revealing sensitive information about the server environment. Although direct reading or modification of file contents is not possible, in some configurations, incomplete cleanup of temporary files can inadvertently expose the NTLM hash of the Windows account under which the Umbraco application runs. This hash exposure could facilitate offline brute-force attacks to recover credentials, potentially leading to privilege escalation or lateral movement within the network. The vulnerability requires authenticated access to the backoffice, does not require user interaction, and has a CVSS v3.1 base score of 4.9 (medium severity), reflecting its moderate impact on confidentiality without affecting integrity or availability. The issue was publicly disclosed on December 9, 2025, and is addressed in Umbraco CMS version 13.12.1.
Potential Impact
For European organizations using affected versions of Umbraco CMS, this vulnerability poses a risk of sensitive information exposure through file enumeration and potential NTLM hash leakage. Attackers with backoffice access could map the server filesystem, gaining insights into server configuration and potentially identifying further attack vectors. Exposure of NTLM hashes is particularly concerning in Windows-dominant environments common in Europe, as it can lead to credential compromise and lateral movement within corporate networks. This can result in unauthorized access to sensitive data, disruption of services, and increased risk of broader compromise. Organizations in sectors with high regulatory requirements, such as finance, healthcare, and government, face increased compliance risks if such exposures lead to data breaches. The requirement for authenticated access limits the threat to insiders or attackers who have already compromised user credentials, but the ease of file enumeration and hash exposure increases the risk of privilege escalation and extended network compromise.
Mitigation Recommendations
European organizations should immediately upgrade all Umbraco CMS instances to version 13.12.1 or later to remediate this vulnerability. Until upgrades are applied, restrict backoffice access strictly to trusted personnel and enforce strong authentication mechanisms, including multi-factor authentication, to reduce the risk of credential compromise. Implement rigorous monitoring and alerting on backoffice access and unusual file system activity to detect exploitation attempts. Review and harden server configurations to ensure temporary files are securely handled and cleaned up promptly, minimizing residual sensitive data exposure. Consider network segmentation to isolate CMS servers from critical infrastructure and limit lateral movement opportunities. Additionally, audit Windows account privileges running the Umbraco application to follow the principle of least privilege, reducing the impact of potential NTLM hash exposure. Regularly update and patch all related infrastructure components and conduct penetration testing focusing on file enumeration and credential exposure vectors.
Affected Countries
Germany, United Kingdom, France, Netherlands, Sweden, Italy, Spain, Poland
CVE-2025-66625: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in umbraco Umbraco-CMS
Description
Umbraco is an ASP.NET CMS. Due to unsafe handling and deletion of temporary files in versions 10.0.0 through 13.12.0, during the dictionary upload process an attacker with access to the backoffice can trigger predictable requests to temporary file paths. The application’s error responses (HTTP 500 when a file exists, 404 when it does not) allow the attacker to enumerate the existence of arbitrary files on the server’s filesystem. This vulnerability does not allow reading or writing file contents. In certain configurations, incomplete clean-up of temporary upload files may additionally expose the NTLM hash of the Windows account running the Umbraco application. This issue is fixed in version 13.12.1.
AI-Powered Analysis
Technical Analysis
Umbraco CMS, an ASP.NET-based content management system, suffers from a vulnerability (CVE-2025-66625) affecting versions 10.0.0 up to but not including 13.12.1. The root cause lies in the unsafe handling and deletion of temporary files generated during the dictionary upload process. An attacker with legitimate backoffice credentials can send crafted requests targeting predictable temporary file paths. The server's error responses differ based on whether the file exists: HTTP 500 if the file is present and HTTP 404 if absent. This discrepancy allows the attacker to enumerate arbitrary files on the server filesystem, revealing sensitive information about the server environment. Although direct reading or modification of file contents is not possible, in some configurations, incomplete cleanup of temporary files can inadvertently expose the NTLM hash of the Windows account under which the Umbraco application runs. This hash exposure could facilitate offline brute-force attacks to recover credentials, potentially leading to privilege escalation or lateral movement within the network. The vulnerability requires authenticated access to the backoffice, does not require user interaction, and has a CVSS v3.1 base score of 4.9 (medium severity), reflecting its moderate impact on confidentiality without affecting integrity or availability. The issue was publicly disclosed on December 9, 2025, and is addressed in Umbraco CMS version 13.12.1.
Potential Impact
For European organizations using affected versions of Umbraco CMS, this vulnerability poses a risk of sensitive information exposure through file enumeration and potential NTLM hash leakage. Attackers with backoffice access could map the server filesystem, gaining insights into server configuration and potentially identifying further attack vectors. Exposure of NTLM hashes is particularly concerning in Windows-dominant environments common in Europe, as it can lead to credential compromise and lateral movement within corporate networks. This can result in unauthorized access to sensitive data, disruption of services, and increased risk of broader compromise. Organizations in sectors with high regulatory requirements, such as finance, healthcare, and government, face increased compliance risks if such exposures lead to data breaches. The requirement for authenticated access limits the threat to insiders or attackers who have already compromised user credentials, but the ease of file enumeration and hash exposure increases the risk of privilege escalation and extended network compromise.
Mitigation Recommendations
European organizations should immediately upgrade all Umbraco CMS instances to version 13.12.1 or later to remediate this vulnerability. Until upgrades are applied, restrict backoffice access strictly to trusted personnel and enforce strong authentication mechanisms, including multi-factor authentication, to reduce the risk of credential compromise. Implement rigorous monitoring and alerting on backoffice access and unusual file system activity to detect exploitation attempts. Review and harden server configurations to ensure temporary files are securely handled and cleaned up promptly, minimizing residual sensitive data exposure. Consider network segmentation to isolate CMS servers from critical infrastructure and limit lateral movement opportunities. Additionally, audit Windows account privileges running the Umbraco application to follow the principle of least privilege, reducing the impact of potential NTLM hash exposure. Regularly update and patch all related infrastructure components and conduct penetration testing focusing on file enumeration and credential exposure vectors.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-12-05T15:18:02.789Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69388517f4a79be77cca2bd3
Added to database: 12/9/2025, 8:22:47 PM
Last enriched: 12/16/2025, 9:44:55 PM
Last updated: 2/7/2026, 11:24:28 AM
Views: 90
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2083: SQL Injection in code-projects Social Networking Site
MediumCVE-2026-2082: OS Command Injection in D-Link DIR-823X
MediumCVE-2026-2080: Command Injection in UTT HiPER 810
HighCVE-2026-2079: Improper Authorization in yeqifu warehouse
MediumCVE-2026-1675: CWE-1188 Initialization of a Resource with an Insecure Default in brstefanovic Advanced Country Blocker
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.