CVE-2023-5074

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2023-09-20. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 68%
CISA-KEV: Not listedEPSS: 68%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Use of a static key to protect a JWT token used in user authentication can allow an for an authentication bypass in D-Link D-View 8 v2.0.1.28

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
86(Attend)
EG Risk 86/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation68% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
99.3%
KEV
Not listed

Published

September 20, 2023

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated May 25, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Authentication Bypass in D-Link D-View 8 - Research Advisory | Tenable®

https://www.tenable.com/security/research/tra-2023-32

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:16 UTCEPSS rescore
  2. 2026-07-23 02:28 UTCEG score recompute
  3. 2026-07-22 23:15 UTCEG score recompute
  4. 2026-07-22 14:07 UTCEPSS rescore
  5. 2026-07-22 14:07 UTCEPSS rescore
  6. 2026-07-21 15:23 UTCEPSS rescore
  7. 2026-07-20 17:06 UTCEPSS rescore
  8. 2026-07-19 14:30 UTCEPSS rescore
  9. 2026-07-19 14:29 UTCEPSS rescore
  10. 2026-07-18 10:03 UTCEPSS rescore
  11. 2026-07-18 10:03 UTCEPSS rescore
  12. 2026-07-16 17:01 UTCEPSS rescore
  13. 2026-07-15 16:56 UTCEPSS rescore
  14. 2026-07-13 06:11 UTCEPSS rescore
  15. 2026-07-12 05:45 UTCEPSS rescore
  16. 2026-07-12 05:45 UTCEPSS rescore
  17. 2026-07-11 08:26 UTCEPSS rescore
  18. 2026-07-09 19:08 UTCEPSS rescore
  19. 2026-07-05 02:29 UTCEPSS rescore
  20. 2026-07-01 15:05 UTCEPSS rescore
  21. 2026-06-30 23:21 UTCEPSS rescore
  22. 2026-06-30 23:21 UTCEPSS rescore
  23. 2026-06-29 14:05 UTCEPSS rescore
  24. 2026-06-28 04:55 UTCEPSS rescore
  25. 2026-06-27 03:07 UTCEPSS rescore
Show 25 more
  1. 2026-06-25 13:48 UTCEPSS rescore
  2. 2026-06-25 13:48 UTCEPSS rescore
  3. 2026-06-24 14:04 UTCEPSS rescore
  4. 2026-06-24 14:04 UTCEPSS rescore
  5. 2026-06-23 21:31 UTCEPSS rescore
  6. 2026-06-23 21:31 UTCEPSS rescore
  7. 2026-06-18 17:51 UTCEPSS rescore
  8. 2026-06-17 17:51 UTCEPSS rescore
  9. 2026-06-16 17:51 UTCEPSS rescore
  10. 2026-06-16 17:51 UTCEPSS rescore
  11. 2026-06-15 17:47 UTCEPSS rescore
  12. 2026-06-14 23:16 UTCEPSS rescore
  13. 2026-06-12 23:11 UTCEPSS rescore
  14. 2026-06-10 22:17 UTCEPSS rescore
  15. 2026-06-10 13:21 UTCEPSS rescore
  16. 2026-06-07 15:24 UTCEPSS rescore
  17. 2026-06-07 15:24 UTCEPSS rescore
  18. 2026-06-05 06:09 UTCEPSS rescore
  19. 2026-06-05 06:09 UTCEPSS rescore
  20. 2026-05-31 22:30 UTCEPSS rescore
  21. 2026-05-31 22:30 UTCEPSS rescore
  22. 2026-05-28 13:44 UTCEPSS rescore
  23. 2026-05-28 13:44 UTCEPSS rescore
  24. 2026-05-24 17:21 UTCEG score recompute
  25. 2026-05-24 17:21 UTCGHSA enrichment

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2023/CVE-2023-5074.yaml
    First seen Jan 1, 2023

    D-Link D-View 8 v2.0.1.28 - Authentication Bypass

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-5074?
CVE-2023-5074 is a critical vulnerability published on September 20, 2023. Use of a static key to protect a JWT token used in user authentication can allow an for an authentication bypass in D-Link D-View 8 v2.0.1.28
When was CVE-2023-5074 disclosed?
CVE-2023-5074 was first published in the National Vulnerability Database on September 20, 2023, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-5074 actively exploited?
CVE-2023-5074 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-5074?
CVE-2023-5074 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2023-5074?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-5074, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-5074

Explore →

Is Your Infrastructure Affected by CVE-2023-5074?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs