CVE-2013-3628 in the critical feed json
Zabbix 2.0.9 has an Arbitrary Command Execution Vulnerability
published 6y ago modified 4mo ago also EUVD-2013-3562
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 67.5%
- EPSS 67.5% chance of exploitation in 30 days, percentile 99.3%
- public exploits
- 2
- Metasploit and Exploit-DB
Summary
Zabbix 2.0.9 has an Arbitrary Command Execution Vulnerability
Is CVE-2013-3628 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit exploit/multi/http/zabbix_script_exec)
- Published
Exploit prediction
67.46% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/multi/http/zabbix_script_exec Zabbix Authenticated Remote Command Execution metasploit exploit, excellent rank, 2013-10-30
- EDB-29321 Zabbix - (Authenticated) Remote Command Execution (Metasploit) remote, 2013-10-31
- community.rapid7.com https://community.rapid7.com/community/metasploit/blog/2013/10/30/seven-tricks-and-treats referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Affected products
- Zabbix Zabbix
Classification
- Weakness
-
- CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component
References
-
community.rapid7.com
/community/metasploit/blog/2013/10/30/seven-tricks-and-treats
exploit, third-party-advisory
-
community.rapid7.com
/community/metasploit/blog/2013/10/30/seven-foss-disclosures-part-one
third-party-advisory
-
securityfocus.com
/bid/63453
third-party-advisory, vdb-entry
-
exploit-db.com
/exploits/29321
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2013-3628
- NVD CVE-2013-3628
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.