How severe is CVE-2020-25223?

CVE-2020-25223 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which products are affected by CVE-2020-25223?

CVE-2020-25223 affects the following products: sophos unified threat management.

How do I patch CVE-2020-25223?

Apply the sophos unified threat management security patch or hotfix for CVE-2020-25223 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2020-25223 across my infrastructure?

Inventory every sophos unified threat management deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2020-25223 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2020-25223?

O3 detects and blocks CVE-2020-25223 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2020-25223 actively exploited in the wild?

Yes. There are 9 known exploit references for CVE-2020-25223, including 7 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-25223?

CVE-2020-25223 has an EPSS (Exploit Prediction Scoring System) score of 96.7%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2020-25223?

CVE-2020-25223 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2020-25223?

CVE-2020-25223 affects sophos unified threat management (3 versions, e.g. 9.511, 9.607, 9.705). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2020-25223?

A Nuclei detection template exists for CVE-2020-25223, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2020-25223 published, and has it been updated?

CVE-2020-25223 was published on September 25, 2020 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

Not in CISA KEV

CRITICAL severity

CVE-2020-25223

CRITICAL

CVE-2020-25223 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in sophos unified threat management. 9 public exploit references exist, so weaponization risk is real. O3 Security detects and blocks CVE-2020-25223 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

A remote code execution vulnerability exists in the WebAdmin of Sophos SG UTM before v9.705 MR5, v9.607 MR7, and v9.511 MR11

Published

Sep 25, 2020

Updated

Jun 17, 2026

Affected

1 product

Patched

See advisory

Exploits

9 known

Exploitation data as of Sep 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

CISA’s SSVC triage classifies this CVE as under active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2020-25223.

EPSS Exploitation Probability

via FIRST.org ↗

96.7%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

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-2020-25223 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.

Where this sits among everything scored

Of 368,770 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Description

A remote code execution vulnerability exists in the WebAdmin of Sophos SG UTM before v9.705 MR5, v9.607 MR7, and v9.511 MR11

Affected Products

1 product · 6 configurations

Application

unified threat managementsophos

≥ 9.700 && < 9.705

3 versions

9.5119.6079.705

Exploits & PoCs

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