CVE-2018-6389

HIGHNVD 7.58.7▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.7 because EPSS predicts 73% probability of exploitation within the next 30 days (top 0.6% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

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

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

In WordPress through 4.9.2, unauthenticated attackers can cause a denial of service (resource consumption) by using the large list of registered .js files (from wp-includes/script-loader.php) to construct a series of requests to load every file many times.

CVSS v3
7.5
EG Score
8.7(high)
EG Risk
73(Track)
EG Risk 73/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
Severity87% × 45%
Exploitation73% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.4%
KEV
Not listed

Published

February 6, 2018

Last Modified

November 21, 2024

References (16)

Weakness Classification(1)

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

Data Freshness Timeline

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

Publicly available exploits

(10 references)

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

  • GitHub PoComidsec/CVE-2018-6389
    First seen Nov 13, 2025

    PoC Exploit CVE-2018-6389

    Open source ↗
  • GitHub PoCianxtianxt/CVE-2018-6389
    First seen Dec 22, 2019

    CVE-2018-6389: WordPress <= 4.9.x 拒绝服务(DOS)漏洞

    Open source ↗
  • GitHub PoCZazzzles/Wordpress-DOS
    First seen Oct 28, 2018

    Exploit for vulnerability CVE-2018-6389 on wordpress sites

    Open source ↗
  • GitHub PoCItinerisLtd/trellis-cve-2018-6389
    First seen Aug 30, 2018

    Mitigate CVE-2018-6389 WordPress load-scripts / load-styles attacks

    Open source ↗
  • GitHub PoCm3ssap0/wordpress_cve-2018-6389
    First seen Mar 4, 2018

    Tries to exploit a WordPress vulnerability (CVE-2018-6389) which can be used to cause a Denial of Service.

    Open source ↗
  • GitHub PoCs0md3v/Shiva
    First seen Mar 4, 2018

    Improved DOS exploit for wordpress websites (CVE-2018-6389)

    Open source ↗
  • GitHub PoCJavierOlmedo/wordpress-cve-2018-6389
    First seen Mar 1, 2018

    CVE-2018-6389 WordPress Core - 'load-scripts.php' Denial of Service <= 4.9.4

    Open source ↗
  • GitHub PoCdsfau/wordpress-CVE-2018-6389
    First seen Feb 9, 2018

    Metasploit module for WordPress DOS load-scripts.php CVE-2018-638

    Open source ↗
  • GitHub PoCknqyf263/CVE-2018-6389
    First seen Feb 7, 2018

    WordPress DoS (CVE-2018-6389)

    Open source ↗
  • GitHub PoCsafebuffer/CVE-2018-6389
    First seen Feb 6, 2018

    CVE-2018-6389 Exploit In WordPress DoS

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-6389?
CVE-2018-6389 is a high vulnerability published on February 6, 2018. In WordPress through 4.9.2, unauthenticated attackers can cause a denial of service (resource consumption) by using the large list of registered .js files (from wp-includes/script-loader.php) to construct a series of requests to load every file many times.
When was CVE-2018-6389 disclosed?
CVE-2018-6389 was first published in the National Vulnerability Database on February 6, 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-6389 actively exploited?
CVE-2018-6389 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-6389?
CVE-2018-6389 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.7.
How do I remediate CVE-2018-6389?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-6389, 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-6389

Explore →

Is Your Infrastructure Affected by CVE-2018-6389?

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

Start Free Scan →Browse All CVEs