Skip to content
Fencer Vulns
high 8.8

CVE-2020-10808 in the critical feed json

Vesta Control Panel (VestaCP) through 0.9.8-26 allows Command Injection via the schedule/backup Backup Listing Endpoint.

published 2020-03-22 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-3214

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
77.5%
EPSS 77.5% chance of exploitation in 30 days, percentile 99.5%
public exploits
1
Metasploit

Summary

Vesta Control Panel (VestaCP) through 0.9.8-26 allows Command Injection via the schedule/backup Backup Listing Endpoint. The attacker must be able to create a crafted filename on the server, as demonstrated by an FTP session that renames .bash_logout to a .bash_logout' substring followed by shell metacharacters.

Patch / fix

Timeline

  1. First public exploit (Metasploit exploit/linux/http/vestacp_exec)
  2. Published

Exploit prediction

77.50% chance of exploitation in the next 30 days, higher than 99.5% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Metasploit exploit/linux/http/vestacp_exec Vesta Control Panel Authenticated Remote Code Execution metasploit exploit, excellent rank, 2020-03-17
  • pentest.blog https://pentest.blog/vesta-control-panel-second-order-remote-code-execution-0day-step-by-step-analysis/ referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/157111/Vesta-Control-Panel-Authenticated-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/157219/Vesta-Control-Panel-Authenticated-Remote-Code-Execution.html 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 9.0 AV:N/AC:L/Au:S/C:C/I:C/A:C

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command

References

Sources

Fencer Vulns 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.