CVE-2020-8657

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.

CVSS: 9.8Criticalscored by CISA
Exploited in the wild: Yes, in CISA KEV since 3 Nov 2021CISA deadline for US federal agencies: 3 May 2022public exploit code
EPSS: 91.9%chance of exploitation in the next 30 daystop 0.2% of scored CVEsFIRST score of 11 Nov 2026
Fix: Not stated by the vendorno fixed release in the CVE record
Published: 6 Feb 2020analysed here 12 Nov 2026

Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface: Server-side
Exploitable: Configuration or build time
Attack vector: network
Weakness: CWE-798 Hard-coded Credentials
Can a WAF block it?: No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

eyesofnetwork:eyesofnetwork

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. Hard-coded credentials let attackers log in normally. A WAF cannot tell their logins from real ones.

Also consider: patch · rotate

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog: Listed since 3 Nov 2021.
CISA due date: 3 May 2022, the remediation deadline for US federal agencies
CISA required action: Apply updates per vendor instructions.
Public exploit code: Yes: 1 on Exploit-DB · 1 Metasploit module · 1 Nuclei template
CISA SSVC: exploitation active, automatable yes, technical impact totalAssessed by CISA 4 Feb 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

6 Feb 2020Published
5 Mar 2020First public exploit or proof of concept27 days later
3 Nov 2021Added to CISA KEV (exploited in the wild)608 days (about 2 years) later
3 May 2022CISA remediation due date (US federal agencies)181 days (about 6 months) later
4 Feb 2025CISA SSVC assessment: exploitation active1,009 days (about 3 years) later
21 Oct 2025CVE record last updated259 days (about 9 months) later
12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Metric	Value	What it means
Attack vector	NetworkReachable over the internet or any routable network.	Reachable over the internet or any routable network.
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	NoneThe attacker needs no prior access.	The attacker needs no prior access.
User interaction	NoneNo victim action needed.	No victim action needed.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	HighTotal data disclosure possible.	Total data disclosure possible.
Integrity	HighComplete modification possible.	Complete modification possible.
Availability	HighFull outage possible.	Full outage possible.

Common questions

Is CVE-2020-8657 being exploited?

Yes. CVE-2020-8657 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2020-8657?

CVE-2020-8657 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2020-8657?

Not known from our data. No patch reference has been recorded for CVE-2020-8657, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2020-8657 affect?

CVE-2020-8657 affects eyesofnetwork:eyesofnetwork. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVD CVE.org CVE Details Source

3 references in the CVE record, grouped by the tags the record gives them.

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA KEV catalog: exploitation, date added, due date
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
Exploit-DB: published exploits
Metasploit Framework: exploit and scanner modules
Nuclei templates: detection templates

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.