CVE-2019-16113

HIGHNVD 8.89.0▲
EchelonGraph scoreHIGH confidence

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

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

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

Bludit 3.9.2 allows remote code execution via bl-kernel/ajax/upload-images.php because PHP code can be entered with a .jpg file name, and then this PHP code can write other PHP code to a ../ pathname.

CVSS v3
8.8
EG Score
9.0(high)
EG Risk
76(Track)
EG Risk 76/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%
Exploitation78% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.5%
KEV
Not listed

Published

September 8, 2019

Last Modified

November 21, 2024

References (8)

Weakness Classification(2)

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

Data Freshness Timeline

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

Publicly available exploits

(7 references)

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

  • Exploit-DBEDB-48701
    First seen Jul 26, 2020

    Bludit 3.9.2 - Directory Traversal

    Open source ↗
  • Exploit-DBEDB-48568
    First seen Jun 9, 2020

    Bludit 3.9.12 - Directory Traversal

    Open source ↗
  • GitHub PoChg8/CVE-2019-16113-PoC
    First seen Jun 9, 2020

    Bludit >= 3.9.2 - Authenticated RCE (CVE-2019-16113)

    Open source ↗
  • GitHub PoCcybervaca/CVE-2019-16113
    First seen Jun 4, 2020

    CVE-2019-16113 - bludit >= 3.9.2 RCE authenticate

    Open source ↗
  • GitHub PoCynots0ups/CVE-2019-16113
    First seen Jun 3, 2020
    Open source ↗
  • Exploit-DBEDB-47699✓ verified
    First seen Nov 20, 2019

    Bludit - Directory Traversal Image File Upload (Metasploit)

    Open source ↗
  • Metasploitexploit/linux/http/bludit_upload_images_exec✓ verified
    First seen Sep 7, 2019

    Bludit Directory Traversal Image File Upload Vulnerability

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-16113?
CVE-2019-16113 is a high vulnerability published on September 8, 2019. Bludit 3.9.2 allows remote code execution via bl-kernel/ajax/upload-images.php because PHP code can be entered with a .jpg file name, and then this PHP code can write other PHP code to a ../ pathname.
When was CVE-2019-16113 disclosed?
CVE-2019-16113 was first published in the National Vulnerability Database on September 8, 2019, 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-2019-16113 actively exploited?
CVE-2019-16113 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-16113?
CVE-2019-16113 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2019-16113?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-16113, 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-2019-16113

Explore →

Is Your Infrastructure Affected by CVE-2019-16113?

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

Start Free Scan →Browse All CVEs