CVE-2018-7357

MEDIUMNVD 6.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 88% probability of exploitation within the next 30 days (top 0.3% of all CVEs). NVD baseline CVSS 6.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Trending — 3 sources updated this weekWeaponized
6.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 88%
CISA-KEV: Not listedEPSS: 88%CVSS: 6.5Exploit: NoneExposed: 0

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

ZTE ZXHN H168N product with versions V2.2.0_PK1.2T5, V2.2.0_PK1.2T2, V2.2.0_PK11T7 and V2.2.0_PK11T have an improper access control vulnerability, which may allow an unauthorized user to gain unauthorized access.

CVSS v3
6.5
EG Score
9.0(high)
EG Risk
80(Track)
EG Risk 80/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
Severity90% × 45%
Exploitation88% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.7%
KEV
Not listed

Published

November 14, 2018

Last Modified

November 21, 2024

References (4)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 18× 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 01:37 UTCEG score recompute
  2. 2026-07-22 21:29 UTCEG score recompute▲ 0.20
  3. 2026-07-22 21:29 UTCGHSA enrichment
  4. 2026-07-22 14:05 UTCEPSS rescore
  5. 2026-07-21 15:22 UTCEPSS rescore
  6. 2026-07-15 16:55 UTCEPSS rescore
  7. 2026-07-12 05:43 UTCEPSS rescore
  8. 2026-07-09 19:06 UTCEPSS rescore
  9. 2026-07-07 13:42 UTCEPSS rescore
  10. 2026-07-07 13:42 UTCEPSS rescore
  11. 2026-07-04 06:28 UTCEPSS rescore
  12. 2026-07-04 06:28 UTCEPSS rescore
  13. 2026-06-30 23:20 UTCEPSS rescore
  14. 2026-06-30 23:20 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-23 21:30 UTCEPSS rescore
  18. 2026-06-23 21:30 UTCEPSS rescore
  19. 2026-06-17 17:50 UTCEPSS rescore
  20. 2026-06-15 17:45 UTCEPSS rescore
  21. 2026-06-14 23:15 UTCEPSS rescore
  22. 2026-06-14 23:15 UTCEPSS rescore
  23. 2026-06-13 22:58 UTCEPSS rescore
  24. 2026-06-12 23:09 UTCEPSS rescore
  25. 2026-06-12 23:09 UTCEPSS rescore
Show 28 more
  1. 2026-06-11 13:57 UTCEPSS rescore
  2. 2026-06-10 22:16 UTCEPSS rescore
  3. 2026-06-10 13:19 UTCEPSS rescore
  4. 2026-06-07 15:22 UTCEPSS rescore
  5. 2026-06-07 15:22 UTCEPSS rescore
  6. 2026-06-06 13:45 UTCEPSS rescore
  7. 2026-06-06 13:45 UTCEPSS rescore
  8. 2026-06-05 22:45 UTCEPSS rescore
  9. 2026-06-05 22:45 UTCEPSS rescore
  10. 2026-06-05 06:08 UTCEPSS rescore
  11. 2026-06-05 06:08 UTCEPSS rescore
  12. 2026-06-04 13:10 UTCEPSS rescore
  13. 2026-06-04 13:10 UTCEPSS rescore
  14. 2026-06-02 20:11 UTCEPSS rescore
  15. 2026-05-31 22:29 UTCEPSS rescore
  16. 2026-05-31 22:29 UTCEPSS rescore
  17. 2026-05-31 00:14 UTCEPSS rescore
  18. 2026-05-31 00:14 UTCEPSS rescore
  19. 2026-05-29 13:41 UTCEPSS rescore
  20. 2026-05-28 13:43 UTCEPSS rescore
  21. 2026-05-28 13:42 UTCEPSS rescore
  22. 2026-05-28 01:07 UTCEG score recompute
  23. 2026-05-28 01:07 UTCGHSA enrichment
  24. 2026-05-27 13:38 UTCEPSS rescore
  25. 2026-05-26 13:42 UTCEPSS rescore
  26. 2026-05-26 13:42 UTCEPSS rescore
  27. 2026-05-26 07:17 UTCEPSS rescore
  28. 2026-05-26 07:17 UTCEPSS rescore

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-45972✓ verified
    First seen Dec 11, 2018

    ZTE ZXHN H168N - Improper Access Restrictions

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-7357?
CVE-2018-7357 is a medium vulnerability published on November 14, 2018. ZTE ZXHN H168N product with versions V2.2.0PK1.2T5, V2.2.0PK1.2T2, V2.2.0PK11T7 and V2.2.0PK11T have an improper access control vulnerability, which may allow an unauthorized user to gain unauthorized access.
When was CVE-2018-7357 disclosed?
CVE-2018-7357 was first published in the National Vulnerability Database on November 14, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-7357 actively exploited?
CVE-2018-7357 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-7357?
CVE-2018-7357 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2018-7357?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-7357, 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-2018-7357

Explore →

Is Your Infrastructure Affected by CVE-2018-7357?

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

Start Free Scan →Browse All CVEs