CVE-2025-24012 is a medium-severity (CVSS 4.6) Cross-site Scripting (XSS) vulnerability in @umbraco-cms/backoffice. A fix is available for @umbraco-cms/backoffice — see the affected versions and patch details below.
Umbraco Backoffice Components Have XSS/HTML Injection Vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-24012.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-24012 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@umbraco-cms/backofficenpmDescription
Umbraco is a free and open source .NET content management system. Starting in version 14.0.0 and prior to versions 14.3.2 and 15.1.2, authenticated users are able to exploit a cross-site scripting vulnerability when viewing certain localized backoffice components. Versions 14.3.2 and 15.1.2 contain a patch.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @umbraco-cms/backoffice | ≥ 14.0.0&&< 14.3.2 | 14.3.2npm install @umbraco-cms/backoffice@14.3.2 |
| 📦npm | @umbraco-cms/backoffice | ≥ 15.0.0&&< 15.1.2 | 15.1.2npm install @umbraco-cms/backoffice@15.1.2 |
| .NETNuGet | Umbraco.Cms.StaticAssets | ≥ 14.0.0&&< 14.3.2 | 14.3.2dotnet add package Umbraco.Cms.StaticAssets --version 14.3.2 |
| .NETNuGet | Umbraco.Cms.StaticAssets | ≥ 15.0.0&&< 15.1.2 | 15.1.2dotnet add package Umbraco.Cms.StaticAssets --version 15.1.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @umbraco-cms/backoffice, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @umbraco-cms/backoffice to 14.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-24012 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-24012 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-24012. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-24012 in your dependencies?
O3 Security finds CVE-2025-24012 across npm, NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.