Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2020-11800: Zabbix Server 2.2.x and 3.0.x before 3.0.31, and 3.2 allows remote attackers to execute arbitrary code.

CriticalCVSS 9.8 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: Plan (action score 42/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 9.1% (FIRST EPSS); higher than 95.3% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: zabbix (Debian:12) 1:4.0.0+dfsg-1; zabbix (Debian:9) 1:3.0.31+dfsg-0+deb9u1; zabbix (openSUSE:Leap 15.1) 3.0.31-bp152.2.3.1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to zabbix (Debian:12) 1:4.0.0+dfsg-1; zabbix (Debian:9) 1:3.0.31+dfsg-0+deb9u1; zabbix (openSUSE:Leap 15.1) 3.0.31-bp152.2.3.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Published
Oct 7, 2020
Updated
Jun 16, 2026
EPSS
9.1% · 95th percentile
CWE
—

Report tools

JSON

Action score

42

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
3 / 30 · 9.1%

CNA vs NVD score

NVD
9.8
CNA · mitre
9.0
0.8 point gap

CVSS:3.0/AC:H/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2020-11800

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
zabbixzabbix
opensusebackports sle
opensuseleap
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux9.0
  • opensuse backports sle15.0
  • opensuse leap15.1
  • opensuse leap15.2
  • zabbix zabbix2.2.0 and later · before 3.0.31
  • zabbix zabbix3.2.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12zabbixbefore 1:4.0.0+dfsg-11:4.0.0+dfsg-1
Debian:9zabbixbefore 1:3.0.31+dfsg-0+deb9u11:3.0.31+dfsg-0+deb9u1
openSUSE:Leap 15.1zabbixbefore 3.0.31-bp152.2.3.13.0.31-bp152.2.3.1
SUSE:Package Hub 15 SP1zabbixbefore 3.0.31-bp152.2.3.13.0.31-bp152.2.3.1

Other highest-scoring records for the same primary product.

  • CVE-2022-23131Unsafe client-side session storage leading to authentication bypass/instance takeover via Zabbix Frontend with configured SAMLKEV
    98Now
  • CVE-2022-23134Possible view of the setup pages by unauthenticated users if config file already existsKEV
    80Now
  • CVE-2016-10134SQL injection vulnerability in Zabbix before 2.2.14 and 3.0 before 3.0.4 allows remote attackers to execute arbitrary SQL commands via the…
    64This week

Published before and after this one in the same product

  • ← EarlierCVE-2013-3738Feb 17, 2020 · A File Inclusion vulnerability exists in Zabbix 2.0.6 due to inadequate sanitization of request strings in CGI scripts, which could let a…
    40Plan
  • ← EarlierCVE-2020-15803Jul 16, 2020 · Zabbix before 3.0.32rc1, 4.x before 4.0.22rc1, 4.1.x through 4.4.x before 4.4.10rc1, and 5.x before 5.0.2rc1 allows stored XSS in the URL…
    34Monitor
  • Later →CVE-2021-27927Mar 3, 2021 · In Zabbix from 4.0.x before 4.0.28rc1, 5.0.0alpha1 before 5.0.10rc1, 5.2.x before 5.2.6rc1, and 5.4.0alpha1 before 5.4.0beta2, the…
    36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:zabbix1:4.0.0+dfsg-1 · Debian:12Package registry (OSV)
opensuse:zabbix3.0.31-bp152.2.3.1 · openSUSE:Leap 15.1Package registry (OSV)
suse:zabbix3.0.31-bp152.2.3.1 · SUSE:Package Hub 15 SP1Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-05-06

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+2036 d
  3. TodayNov 12, 2026+2227 d

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records