Skip to content
Fencer Intel
high 7.5

CVE-2014-4511 in the critical feed json

Gitlist before 0.5.0 allows remote attackers to execute arbitrary commands via shell metacharacters in the file name in the URI of a reques…

published 2014-07-22 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-4438

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
82.7%
EPSS 82.7% chance of exploitation in 30 days, percentile 99.6%
public exploits
3
Metasploit, Exploit-DB

Summary

Gitlist before 0.5.0 allows remote attackers to execute arbitrary commands via shell metacharacters in the file name in the URI of a request for a (1) blame, (2) file, or (3) stats page, as demonstrated by requests to blame/master/, master/, and stats/master/.

Timeline

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

Exploit prediction

82.73% chance of exploitation in the next 30 days, higher than 99.6% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/linux/http/gitlist_exec Gitlist Unauthenticated Remote Command Execution metasploit exploit, excellent rank, 2014-06-30
  • EDB-33990 Gitlist - Remote Command Execution (Metasploit) remote, 2014-07-07
  • EDB-33929 Gitlist 0.4.0 - Remote Code Execution remote, 2014-06-30
  • hatriot.github.io http://hatriot.github.io/blog/2014/06/29/gitlist-rce/ referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/127281/Gitlist-0.4.0-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/127364/Gitlist-Unauthenticated-Remote-Command-Execution.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

References

Sources

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.