CVE-2023-5684

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 78.4%, top 0% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Weaponized
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 78%
  • Public exploit code is available (ssvc poc, epss top5pct, epss high)
CISA-KEV: Not listedEPSS PROB: 78%CVSS: 9.8Exploit: ssvc poc · epss top5pct · epss highExposed: 0

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

A vulnerability was found in Byzoro Smart S85F Management Platform up to 20231012. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /importexport.php. The manipulation leads to os command injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-243061 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Track)
EG Risk 75/100SSVC: Track

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%
Exploitation78% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
78%
EPSS %ILE
100%
KEV
Not listed

Published

October 21, 2023

Last Modified

June 17, 2026

References (8)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 20× 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-25 14:16 UTCEPSS rescore
  2. 2026-07-24 14:16 UTCEPSS rescore
  3. 2026-07-23 02:30 UTCEG score recompute
  4. 2026-07-22 23:16 UTCEG score recompute 5.10
  5. 2026-07-22 14:07 UTCEPSS rescore
  6. 2026-07-22 14:07 UTCEPSS rescore
  7. 2026-07-21 15:23 UTCEPSS rescore
  8. 2026-07-18 10:03 UTCEPSS rescore
  9. 2026-07-18 10:03 UTCEPSS rescore
  10. 2026-07-15 16:56 UTCEPSS rescore
  11. 2026-07-13 22:28 UTCEPSS rescore
  12. 2026-07-13 22:28 UTCEPSS rescore
  13. 2026-07-09 19:08 UTCEPSS rescore
  14. 2026-07-07 13:45 UTCEPSS rescore
  15. 2026-07-07 13:44 UTCEPSS rescore
  16. 2026-07-01 15:05 UTCEPSS rescore
  17. 2026-06-30 23:21 UTCEPSS rescore
  18. 2026-06-30 23:21 UTCEPSS rescore
  19. 2026-06-29 14:05 UTCEPSS rescore
  20. 2026-06-28 04:55 UTCEPSS rescore
  21. 2026-06-25 13:48 UTCEPSS rescore
  22. 2026-06-25 13:48 UTCEPSS rescore
  23. 2026-06-24 14:04 UTCEPSS rescore
  24. 2026-06-24 14:04 UTCEPSS rescore
  25. 2026-06-24 06:25 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
Show 42 more
  1. 2026-06-23 21:31 UTCEPSS rescore
  2. 2026-06-23 21:31 UTCEPSS rescore
  3. 2026-06-19 19:24 UTCEPSS rescore
  4. 2026-06-19 19:24 UTCEPSS rescore
  5. 2026-06-17 17:51 UTCEPSS rescore
  6. 2026-06-15 17:47 UTCEPSS rescore
  7. 2026-06-13 22:59 UTCEPSS rescore
  8. 2026-06-13 22:59 UTCEPSS rescore
  9. 2026-06-12 23:11 UTCEPSS rescore
  10. 2026-06-11 13:59 UTCEPSS rescore
  11. 2026-06-10 22:17 UTCEPSS rescore
  12. 2026-06-10 13:21 UTCEPSS rescore
  13. 2026-06-08 14:16 UTCEPSS rescore
  14. 2026-06-08 14:16 UTCEPSS rescore
  15. 2026-06-07 15:24 UTCEPSS rescore
  16. 2026-06-07 15:24 UTCEPSS rescore
  17. 2026-06-06 13:46 UTCEPSS rescore
  18. 2026-06-06 13:46 UTCEPSS rescore
  19. 2026-06-05 22:46 UTCEPSS rescore
  20. 2026-06-05 22:46 UTCEPSS rescore
  21. 2026-06-05 06:09 UTCEPSS rescore
  22. 2026-06-05 06:09 UTCEPSS rescore
  23. 2026-06-04 13:11 UTCEPSS rescore
  24. 2026-06-04 13:11 UTCEPSS rescore
  25. 2026-06-02 20:12 UTCEPSS rescore
  26. 2026-06-02 20:12 UTCEPSS rescore
  27. 2026-06-01 13:51 UTCEPSS rescore
  28. 2026-05-31 22:30 UTCEPSS rescore
  29. 2026-05-31 22:30 UTCEPSS rescore
  30. 2026-05-31 00:15 UTCEPSS rescore
  31. 2026-05-31 00:15 UTCEPSS rescore
  32. 2026-05-29 13:43 UTCEPSS rescore
  33. 2026-05-28 13:44 UTCEPSS rescore
  34. 2026-05-28 13:44 UTCEPSS rescore
  35. 2026-05-27 13:40 UTCEPSS rescore
  36. 2026-05-27 13:39 UTCEPSS rescore
  37. 2026-05-26 13:43 UTCEPSS rescore
  38. 2026-05-26 13:43 UTCEPSS rescore
  39. 2026-05-26 07:18 UTCEPSS rescore
  40. 2026-05-26 07:18 UTCEPSS rescore
  41. 2026-05-24 15:24 UTCEG score recompute
  42. 2026-05-24 15:24 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2023-5684?
CVE-2023-5684 is a critical vulnerability published on October 21, 2023. A vulnerability was found in Byzoro Smart S85F Management Platform up to 20231012. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /importexport.php. The manipulation leads to os command injection. The attack can be launched remotely. The…
When was CVE-2023-5684 disclosed?
CVE-2023-5684 was first published in the National Vulnerability Database on October 21, 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-5684 actively exploited?
CVE-2023-5684 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 78% probability of exploitation in the next 30 days, which ranks it in the top 0.5% of all scored CVEs.
What is the CVSS score of CVE-2023-5684?
CVE-2023-5684 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2023-5684?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-5684, 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-5684

Explore →

Is Your Infrastructure Affected by CVE-2023-5684?

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