Skip to content
Fencer Intel
critical 9.8

CVE-2020-8656 in the critical feed json

An issue was discovered in EyesOfNetwork 5.3.

published 6y ago modified 4mo ago also EUVD-2020-29504

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
84.6%
EPSS 84.6% chance of exploitation in 30 days, percentile 99.7%
public exploits
3
Metasploit and Exploit-DB, plus a Nuclei check

Summary

An issue was discovered in EyesOfNetwork 5.3. The EyesOfNetwork API 2.4.2 is prone to SQL injection, allowing an unauthenticated attacker to perform various tasks such as authentication bypass via the username field to getApiKey in include/api_functions.php.

Is CVE-2020-8656 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 Fencer

Timeline

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

Exploit prediction

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

Exploits and checks

  • Metasploit exploit/linux/http/eyesofnetwork_autodiscovery_rce EyesOfNetwork 5.1-5.3 AutoDiscovery Target Command Execution metasploit exploit, excellent rank, 2020-02-06
  • EDB-48169 EyesOfNetwork - AutoDiscovery Target Command Execution (Metasploit) remote, 2020-03-05
  • EDB-48025 EyesOfNetwork 5.3 - Remote Code Execution webapps, 2020-02-07
  • Nuclei template EyesOfNetwork - Hardcoded API Key & SQL Injection nuclei detection template
  • packetstormsecurity.com http://packetstormsecurity.com/files/156266/EyesOfNetwork-5.3-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/156605/EyesOfNetwork-AutoDiscovery-Target-Command-Execution.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

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.