NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
MEDIUM severity

CVE-2020-7210 — UmbracoCMS.Core

MEDIUM

CVE-2020-7210 is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in UmbracoCMS.Core. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for UmbracoCMS.Core — see the affected versions and patch details below.

Umbraco CMS vulnerable to CSRF

Also known asGHSA-gqqf-8cx6-9r7h
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
4 known
Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk
0.00%0.51%1.02%1.54%0.2%1.0%Apr 26Aug 26Oct 26

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

1 pkg affected
.NETUmbracoCMS.Core

Real-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

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetUmbracoCMS.Coreall versions8.5.0dotnet add package UmbracoCMS.Core --version 8.5.0

Affected Products

1 product · 1 configurations
Application
umbraco cmsumbraco
1 version
8.2.2
Exploits & PoCs
4

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for UmbracoCMS.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. 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.

  3. 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.

Frequently Asked Questions

Umbraco CMS 8.2.2 allows CSRF to enable/disable or delete user accounts.
O3 Security · Impact-Aware SCA

Is CVE-2020-7210 in your dependencies?

Find it across NuGet, including transitive dependencies.

CVE-2020-7210: UmbracoCMS.Core CSRF — Fixed in 8.5.0