CVE-2024-35240 — Umbraco.Commerce
MEDIUMCVE-2024-35240 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in Umbraco.Commerce. A fix is available for Umbraco.Commerce — see the affected versions and patch details below.
Umbraco Commerce vulnerable to Stored Cross-site Scripting on Print Functionality
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-2024-35240.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
Umbraco.Commerce.NETUmbraco.CommerceReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Umbraco Commerce is an open source dotnet ecommerce solution. In affected versions there exists a stored Cross-site scripting (XSS) issue which would enable attackers to inject malicious code into Print Functionality. This issue has been addressed in versions 12.1.4, and 10.0.5. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Umbraco.Commerce | ≥ 12.0.0&&< 12.1.4 | 12.1.4dotnet add package Umbraco.Commerce --version 12.1.4 |
| .NETNuGet | Umbraco.Commerce | all versions | 10.0.5dotnet add package Umbraco.Commerce --version 10.0.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Umbraco.Commerce, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Umbraco.Commerce to 12.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-35240 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2024-35240 in your dependencies?
Find it across NuGet, including transitive dependencies.