CVE-2018-19991

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.3%CVSS: 9.8Exploit: None knownExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2018 — isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

VeryNginx 0.3.3 allows remote attackers to bypass the Web Application Firewall feature because there is no error handler (for get_uri_args or get_post_args) to block the API misuse described in CVE-2018-9230.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
50
EG Risk 50/100

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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability30% × 15%
EchelonGraph's default before algorithm v3.4: CISA had not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix has been recorded since the CVE record was published in 2018. Isolate the affected system within your standard update timelines at low or medium mission impact and sooner than that at high (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
2.3%
EPSS %ILE
83rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).

No fix has been recorded since the CVE record was published in 2018. Isolate the affected system within your standard update timelines at low or medium mission impact and sooner than that at high (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

Published

December 10, 2018

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Oct 6, 2026
No fix on record since 2018.
generic

args block can be bypassed because of the lack of error handle · Issue #218 · alexazhou/VeryNginx · GitHub

https://github.com/alexazhou/VeryNginx/issues/218

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 25× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 89 of 158 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 11 repeat rows among the latest 100 are merged into the row they repeat. The 69 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 13:41 UTCEPSS rescoreEPSS 2.3% · 83rd percentile
  2. 2026-10-10 19:55 UTCEPSS rescoreEPSS 2.3% · 83rd percentile
  3. 2026-10-09 20:02 UTCEPSS rescoreEPSS 2.3% · 83rd percentile
  4. 2026-10-08 16:36 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  5. 2026-10-07 23:42 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  6. 2026-10-06 15:12 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  7. 2026-10-05 17:39 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  8. 2026-10-04 23:18 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  9. 2026-10-03 14:21 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  10. 2026-10-01 19:44 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  11. 2026-09-30 14:59 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  12. 2026-09-30 09:59 UTCEG score recompute
  13. 2026-09-28 15:43 UTCOSV refresh
  14. 2026-09-28 13:45 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  15. 2026-09-27 13:40 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  16. 2026-09-26 15:53 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  17. 2026-09-24 13:59 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  18. 2026-09-20 20:10 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  19. 2026-09-19 15:36 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  20. 2026-09-18 19:22 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  21. 2026-09-17 19:22 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  22. 2026-09-16 05:06 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  23. 2026-09-15 03:05 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  24. 2026-09-13 16:42 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  25. 2026-09-12 14:56 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
Show 64 more
  1. 2026-09-11 14:47 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  2. 2026-09-11 09:32 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  3. 2026-09-08 20:34 UTCOSV refresh
  4. 2026-09-07 15:57 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  5. 2026-09-06 13:43 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  6. 2026-09-05 15:24 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  7. 2026-09-04 13:56 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  8. 2026-09-04 05:02 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  9. 2026-09-02 14:07 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  10. 2026-09-01 13:49 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  11. 2026-09-01 03:32 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  12. 2026-08-28 21:36 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  13. 2026-08-27 14:21 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  14. 2026-08-26 14:42 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  15. 2026-08-25 13:44 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  16. 2026-08-22 05:37 UTCOSV refresh
  17. 2026-08-21 23:45 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  18. 2026-08-20 22:51 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  19. 2026-08-19 17:00 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  20. 2026-08-18 13:44 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  21. 2026-08-17 13:43 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  22. 2026-08-16 14:51 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  23. 2026-08-16 02:10 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  24. 2026-08-15 01:26 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  25. 2026-08-13 21:56 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  26. 2026-08-12 13:46 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  27. 2026-08-09 13:43 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  28. 2026-08-08 16:32 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  29. 2026-08-07 16:23 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  30. 2026-08-06 13:42 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  31. 2026-08-06 08:40 UTCOSV refresh
  32. 2026-08-05 19:13 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  33. 2026-08-04 15:05 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  34. 2026-08-02 02:23 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  35. 2026-08-01 04:12 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  36. 2026-07-30 16:24 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  37. 2026-07-30 01:27 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  38. 2026-07-28 15:32 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  39. 2026-07-26 14:51 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  40. 2026-07-25 14:14 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  41. 2026-07-24 14:14 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  42. 2026-07-23 14:15 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  43. 2026-07-23 01:35 UTCEG score recompute
  44. 2026-07-22 22:15 UTCEG score recompute
  45. 2026-07-22 14:05 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  46. 2026-07-21 15:22 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  47. 2026-07-21 01:47 UTCOSV refresh
  48. 2026-07-20 17:04 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  49. 2026-07-19 14:28 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  50. 2026-07-19 02:26 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  51. 2026-07-16 16:59 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  52. 2026-07-15 16:55 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  53. 2026-07-15 01:56 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  54. 2026-07-13 22:26 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  55. 2026-07-13 06:10 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  56. 2026-07-12 05:43 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  57. 2026-07-11 08:24 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  58. 2026-07-09 19:06 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  59. 2026-07-08 15:11 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  60. 2026-07-07 13:42 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  61. 2026-07-06 16:24 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  62. 2026-07-06 02:20 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  63. 2026-07-05 02:27 UTCEPSS rescoreEPSS 2.3% · 81st percentile
  64. 2026-07-04 06:28 UTCEPSS rescoreEPSS 2.3% · 81st percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-19991?
CVE-2018-19991 is a critical-severity vulnerability; its CVE record was published on December 10, 2018. VeryNginx 0.3.3 allows remote attackers to bypass the Web Application Firewall feature because there is no error handler (for geturiargs or getpostargs) to block the API misuse described in CVE-2018-9230.
When was CVE-2018-19991 made public?
CVE-2018-19991 was made public on December 9, 2018: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on December 10, 2018. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2018-19991 actively exploited?
CVE-2018-19991 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.3% probability of exploitation in the next 30 days (83rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-19991?
CVE-2018-19991 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-19991?
No fix for CVE-2018-19991 has been recorded since its CVE record was published in 2018, and EchelonGraph holds no vendor advisory for it. Isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2018-19991

Explore →

Is Your Infrastructure Affected by CVE-2018-19991?

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

Book a Demo →Browse All CVEs