CVE-2020-7210
MEDIUMCVE-2020-7210 is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in UmbracoCMS.Core. 4 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2020-7210 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Umbraco CMS vulnerable to CSRF
Real-World Exposure
UmbracoCMS.CoreReal-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 CMS 8.2.2 allows CSRF to enable/disable or delete user accounts.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | UmbracoCMS.Core | all versions | 8.5.0 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Umbraco CMS 8.2.2 allows CSRF to enable/disable or delete user accounts.
Umbraco CMS 8.2.2 allows CSRF to enable/disable or delete user accounts.
Umbraco CMS 8.2.2 allows CSRF to enable/disable or delete user accounts.
Umbraco CMS 8.2.2 allows CSRF to enable/disable or delete user accounts.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for UmbracoCMS.Core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update UmbracoCMS.Core to 8.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7210 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 pinpoints whether CVE-2020-7210 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2020-7210. 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-2020-7210 in your dependencies?
O3 detects CVE-2020-7210 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.