CVE-2016-6195

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 68%
CISA-KEV: Not listedEPSS: 68%CVSS: 9.8Exploit: NoneExposed: 0

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

SQL injection vulnerability in forumrunner/includes/moderation.php in vBulletin before 4.2.2 Patch Level 5 and 4.2.3 before Patch Level 1 allows remote attackers to execute arbitrary SQL commands via the postids parameter to forumrunner/request.php, as exploited in the wild in July 2016.

CVSS v3
9.8
EG Score
9.8(medium)
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
Severity98% × 45%
Exploitation68% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
99.3%
KEV
Not listed

Published

August 30, 2016

Last Modified

May 6, 2026

Advisory Details (3)

Auto-updated May 8, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic🟡 PoC Available

GitHub - datagoboom/vbully: 3.8.x - 4.2.3 ForumRunner (vBulletin) exploit Proof of Concept · GitHub

https://github.com/drewlong/vbully
generic🔴 Active Exploitation

vBulletin <= 4.2.3 SQL Injection – enumerated

https://enumerated.wordpress.com/2016/07/11/1/
generic
http://www.securityfocus.com/bid/92687

Data Freshness Timeline

(refreshed 12× 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-24 14:13 UTCEPSS rescore
  2. 2026-07-23 14:15 UTCEPSS rescore
  3. 2026-07-23 01:23 UTCEG score recompute
  4. 2026-07-22 22:03 UTCEG score recompute
  5. 2026-07-22 14:04 UTCEPSS rescore
  6. 2026-07-21 15:21 UTCEPSS rescore
  7. 2026-07-21 15:21 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-16 16:59 UTCEPSS rescore
  14. 2026-07-16 16:59 UTCEPSS rescore
  15. 2026-07-15 16:54 UTCEPSS rescore
  16. 2026-07-15 16:54 UTCEPSS rescore
  17. 2026-07-13 22:26 UTCEPSS rescore
  18. 2026-07-13 06:09 UTCEPSS rescore
  19. 2026-07-11 08:24 UTCEPSS rescore
  20. 2026-07-09 19:06 UTCEPSS rescore
  21. 2026-07-08 15:10 UTCEPSS rescore
  22. 2026-07-04 06:28 UTCEPSS rescore
  23. 2026-07-01 15:02 UTCEPSS rescore
  24. 2026-06-27 03:05 UTCEPSS rescore
  25. 2026-06-25 13:47 UTCEPSS rescore
Show 50 more
  1. 2026-06-23 21:30 UTCEPSS rescore
  2. 2026-06-22 14:23 UTCEPSS rescore
  3. 2026-06-21 01:57 UTCEPSS rescore
  4. 2026-06-21 01:57 UTCEPSS rescore
  5. 2026-06-18 17:50 UTCEPSS rescore
  6. 2026-06-18 17:50 UTCEPSS rescore
  7. 2026-06-17 17:50 UTCEPSS rescore
  8. 2026-06-17 17:50 UTCEPSS rescore
  9. 2026-06-16 17:50 UTCEPSS rescore
  10. 2026-06-15 17:45 UTCEPSS rescore
  11. 2026-06-13 22:57 UTCEPSS rescore
  12. 2026-06-13 22:57 UTCEPSS rescore
  13. 2026-06-12 23:09 UTCEPSS rescore
  14. 2026-06-11 13:57 UTCEPSS rescore
  15. 2026-06-08 14:14 UTCEPSS rescore
  16. 2026-06-07 15:22 UTCEPSS rescore
  17. 2026-06-07 15:22 UTCEPSS rescore
  18. 2026-06-06 13:45 UTCEPSS rescore
  19. 2026-06-06 13:45 UTCEPSS rescore
  20. 2026-06-05 22:44 UTCEPSS rescore
  21. 2026-06-04 13:10 UTCEPSS rescore
  22. 2026-06-04 13:10 UTCEPSS rescore
  23. 2026-06-01 13:49 UTCEPSS rescore
  24. 2026-06-01 13:49 UTCEPSS rescore
  25. 2026-05-31 22:28 UTCEPSS rescore
  26. 2026-05-31 22:28 UTCEPSS rescore
  27. 2026-05-31 00:14 UTCEPSS rescore
  28. 2026-05-29 13:41 UTCEPSS rescore
  29. 2026-05-28 13:42 UTCEPSS rescore
  30. 2026-05-28 13:42 UTCEPSS rescore
  31. 2026-05-26 13:42 UTCEPSS rescore
  32. 2026-05-26 13:42 UTCEPSS rescore
  33. 2026-05-24 16:44 UTCEPSS rescore
  34. 2026-05-22 21:15 UTCEPSS rescore
  35. 2026-05-20 22:37 UTCEPSS rescore
  36. 2026-05-20 22:37 UTCEPSS rescore
  37. 2026-05-20 22:37 UTCEPSS rescore
  38. 2026-05-20 09:02 UTCGHSA enrichment
  39. 2026-05-20 05:00 UTCGHSA enrichment
  40. 2026-05-20 01:02 UTCGHSA enrichment
  41. 2026-05-19 20:57 UTCGHSA enrichment
  42. 2026-05-19 16:56 UTCGHSA enrichment
  43. 2026-05-19 12:55 UTCGHSA enrichment
  44. 2026-05-19 08:56 UTCGHSA enrichment
  45. 2026-05-19 04:57 UTCGHSA enrichment
  46. 2026-05-19 00:58 UTCEG score recompute
  47. 2026-05-19 00:58 UTCGHSA enrichment
  48. 2026-05-18 21:30 UTCEPSS rescore
  49. 2026-05-18 21:30 UTCEPSS rescore
  50. 2026-05-18 21:30 UTCEPSS rescore

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.

  • Nucleihttp/cves/2016/CVE-2016-6195.yaml
    First seen Jan 1, 2016

    vBulletin <= 4.2.3 - SQL Injection

    Open source ↗
  • Exploit-DBEDB-40751✓ verified
    First seen Aug 25, 2015

    vBulletin 3.6.0 < 4.2.3 - 'ForumRunner' SQL Injection

    Open source ↗

Frequently asked(5)

What is CVE-2016-6195?
CVE-2016-6195 is a critical vulnerability published on August 30, 2016. SQL injection vulnerability in forumrunner/includes/moderation.php in vBulletin before 4.2.2 Patch Level 5 and 4.2.3 before Patch Level 1 allows remote attackers to execute arbitrary SQL commands via the postids parameter to forumrunner/request.php, as exploited in the wild in July 2016.
When was CVE-2016-6195 disclosed?
CVE-2016-6195 was first published in the National Vulnerability Database on August 30, 2016, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-6195 actively exploited?
CVE-2016-6195 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-2016-6195?
CVE-2016-6195 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2016-6195?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-6195, 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-2016-6195

Explore →

Is Your Infrastructure Affected by CVE-2016-6195?

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

Start Free Scan →Browse All CVEs