CVE-2024-32872 — Umbraco.Workflow
MEDIUMCVE-2024-32872 is a medium-severity (CVSS 5.5) SQL Injection vulnerability in Umbraco.Workflow. A fix is available for Umbraco.Workflow — see the affected versions and patch details below.
Umbraco Workflow's Backoffice users can execute arbitrary SQL
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-32872.
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-2024-32872 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 377,636 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
Umbraco.Workflow.NETUmbraco.Workflow.NETUmbraco.Workflow.NETPlumber.WorkflowReal-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
Impact
Backoffice users can execute arbitrary SQL.
Explanation of the vulnerability
A Backoffice user can modify requests to a particular API endpoint to include SQL which will be executed by the server.
Affected versions
All versions
Patches
Workflow 10.3.9, 12.2.6, 13.0.6, Plumber 10.1.2
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Umbraco.Workflow | all versions | 10.3.9dotnet add package Umbraco.Workflow --version 10.3.9 |
| .NETNuGet | Umbraco.Workflow | ≥ 11.0.0-rc1&&< 12.2.6 | 12.2.6dotnet add package Umbraco.Workflow --version 12.2.6 |
| .NETNuGet | Umbraco.Workflow | ≥ 13.0.0-rc1&&< 13.0.6 | 13.0.6dotnet add package Umbraco.Workflow --version 13.0.6 |
| .NETNuGet | Plumber.Workflow | all versions | 10.1.2dotnet add package Plumber.Workflow --version 10.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.Workflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Umbraco.Workflow to 10.3.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-32872 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-2024-32872 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-32872. 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-2024-32872 in your dependencies?
O3 Security finds CVE-2024-32872 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.