How severe is CVE-2020-8657?

CVE-2020-8657 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-8657?

Affected package information for CVE-2020-8657 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2020-8657?

No fixed version has been published for CVE-2020-8657 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2020-8657 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2020-8657, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-8657?

CVE-2020-8657 has an EPSS (Exploit Prediction Scoring System) score of 88.9%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2020-8657 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2020-8657 (EyesOfNetwork Use of Hard-Coded Credentials Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2020-8657?

CVE-2020-8657 is classified as Hard-coded Credentials (CWE-798). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2020-8657?

A Nuclei detection template exists for CVE-2020-8657, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2020-8657 published, and has it been updated?

CVE-2020-8657 was published on February 6, 2020 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2021-11-03 — agencies required to remediate by 2022-05-03

CVE-2020-8657

CRITICAL

Published

Feb 6, 2020

Updated

Apr 10, 2026

Affected

0 pkgs

Patched

None yet

Exploits

4 known

EPSS Exploitation Probability

via FIRST.org ↗

88.9%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

An issue was discovered in EyesOfNetwork 5.3. The installation uses the same API key (hardcoded as EONAPI_KEY in include/api_functions.php for API version 2.4.2) by default for all installations, hence allowing an attacker to calculate/guess the admin access token.

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-48169remotemultiple✓ Verified

EyesOfNetwork - AutoDiscovery Target Command Execution (Metasploit)

by Metasploit · Mar 5, 2020

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-8657 in your stack?

O3 detects CVE-2020-8657 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works