CVE-2020-5284

MEDIUMNVD 4.44.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.4 under NVD CVSS v3. EPSS exploit probability: 79.8%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
4.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 43%CVSS: 4.4Exploit: NoneExposed: 0

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

Next.js versions before 9.3.2 have a directory traversal vulnerability. Attackers could craft special requests to access files in the dist directory (.next). This does not affect files outside of the dist directory (.next). In general, the dist directory only holds build assets unless your application intentionally stores other assets under this directory. This issue is fixed in version 9.3.2.

CVSS v3
4.4
EG Score
4.4(medium)
EPSS
98.6%
KEV
Not listed

Published

March 30, 2020

Last Modified

November 21, 2024

References (4)

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
next—9.3.2—

Weakness Classification(2)

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

Data Freshness Timeline

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

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/2020/CVE-2020-5284.yaml
    First seen Jan 1, 2020

    Next.js <9.3.2 - Local File Inclusion

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-5284?
CVE-2020-5284 is a medium vulnerability published on March 30, 2020. Next.js versions before 9.3.2 have a directory traversal vulnerability. Attackers could craft special requests to access files in the dist directory (.next). This does not affect files outside of the dist directory (.next). In general, the dist directory only holds build assets unless your…
When was CVE-2020-5284 disclosed?
CVE-2020-5284 was first published in the National Vulnerability Database on March 30, 2020, 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-2020-5284 actively exploited?
CVE-2020-5284 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-5284?
CVE-2020-5284 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2020-5284?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-5284, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-5284

Explore →

Is Your Infrastructure Affected by CVE-2020-5284?

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

Start Free Scan →Browse All CVEs