CVE-2024-55488
MediumCVSS 6.5Exploitation Probability (EPSS)
Low risk23th percentile - higher than 23% of all known CVEs
Summary
A stored cross-site scripting (XSS) vulnerability in Umbraco CMS v14.3.1 allows attackers to execute arbitrary web scripts or HTML via a crafted payload. NOTE: This has been disputed by the vendor since this potential attack is only possible via authenticated users who have been manually allowed access to the CMS. There was a deliberate decision made not to apply HTML sanitization at the product level.
Risk Assessment
The risk for the organization is limited because the exploit requires an authenticated user with access to the CMS. If such a user's account is compromised, an attacker can inject malicious code, potentially leading to session data theft or website defacement.
Recommendation
It is recommended to restrict access to the Umbraco CMS admin panel to trusted users only and implement additional security measures such as Content Security Policy (CSP) and server-side input validation.
Other vulnerabilities in Umbraco CMS
See all- CVE-2025-67288Critical
An arbitrary file upload vulnerability in Umbraco CMS v16.3.3 allows attackers to execute arbitrary code by uploading a crafted PDF file. The supplier disputes this, stating that file validation is the administrator's responsibility and that PDF JavaScript runs in an isolated sandbox.
- CVE-2026-46616Medium
Umbraco is an ASP.NET CMS. Prior to versions 13.14.0 and 17.4.0, some Surface Controllers in the CMS fail to validate redirect URLs, making Razor templates that derive 'RedirectUrl' from user-controlled query parameters vulnerable to malicious redirect attacks.
- CVE-2023-37267High
Umbraco, an ASP.NET CMS, can under rare conditions allow unauthorized users access to admin-level permissions after a restart. This vulnerability was patched in versions 10.6.1, 11.4.2, and 12.0.1.
Original NVD description (English source)
A stored cross-site scripting (XSS) vulnerability in Umbraco CMS v14.3.1 allows attackers to execute arbitrary web scripts or HTML via a crafted payload. NOTE: This has been disputed by the vendor since this potential attack is only possible via authenticated users who have been manually allowed access to the CMS. There was a deliberate decision made not to apply HTML sanitization at the product level.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

