CVE-2018-7490

HIGHNVD 7.58.6▲
EchelonGraph scoreHIGH confidence

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

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

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

uWSGI before 2.0.17 mishandles a DOCUMENT_ROOT check during use of the --php-docroot option, allowing directory traversal.

CVSS v3
7.5
EG Score
8.6(high)
EG Risk
71(Track)
EG Risk 71/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
Severity86% × 45%
Exploitation70% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.3%
KEV
Not listed

Published

February 26, 2018

Last Modified

November 21, 2024

References (6)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
uwsgi1.4.10 ... 2.0.9 (49 versions)2.0.17—

Weakness Classification(1)

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

Data Freshness Timeline

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

Publicly available exploits

(2 references)

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-44223✓ verified
    First seen Mar 2, 2018

    uWSGI < 2.0.17 - Directory Traversal

    Open source ↗
  • Nucleihttp/cves/2018/CVE-2018-7490.yaml
    First seen Jan 1, 2018

    uWSGI PHP Plugin Local File Inclusion

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-7490?
CVE-2018-7490 is a high vulnerability published on February 26, 2018. uWSGI before 2.0.17 mishandles a DOCUMENT_ROOT check during use of the --php-docroot option, allowing directory traversal.
When was CVE-2018-7490 disclosed?
CVE-2018-7490 was first published in the National Vulnerability Database on February 26, 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-7490 actively exploited?
CVE-2018-7490 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-2018-7490?
CVE-2018-7490 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.6.
How do I remediate CVE-2018-7490?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-7490, 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-2018-7490

Explore →

Is Your Infrastructure Affected by CVE-2018-7490?

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

Start Free Scan →Browse All CVEs