CVE-2018-25379

HIGHNVD 8.28.2
EchelonGraph scoreMEDIUM confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-05-26. NVD baseline CVSS 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: Elevated riskExposed: 0

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

Collectric CMU 1.0 contains a boolean-based blind SQL injection vulnerability in the lang parameter that allows unauthenticated attackers to manipulate database queries during authentication. Attackers can inject SQL code through the lang parameter in login requests to extract sensitive information from the database using time-based blind techniques.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
68(Attend)
EG Risk 68/100SSVC: Attend

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
Severity82% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

May 25, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated Jun 3, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

Collectric CMU 1.0 SQL Injection via lang Parameter | Advisories | VulnCheck

https://www.vulncheck.com/advisories/collectric-cmu-sql-injection-via-lang-parameter
generic🟡 PoC Available

Collectric CMU 1.0 - 'lang' Hard-Coded Credentials / SQL injection - Hardware webapps Exploit

https://www.exploit-db.com/exploits/45446

Vendor Advisories for CVE-2018-25379(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 57× 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.

Showing the most recent 100 of 218 total refreshes for this CVE.

  1. 2026-09-04 13:56 UTCEPSS rescore
  2. 2026-09-04 05:02 UTCEPSS rescore
  3. 2026-09-02 14:07 UTCEPSS rescore
  4. 2026-09-01 13:49 UTCEPSS rescore
  5. 2026-08-28 21:36 UTCEPSS rescore
  6. 2026-08-27 14:21 UTCEPSS rescore
  7. 2026-08-26 14:42 UTCEPSS rescore
  8. 2026-08-25 13:44 UTCEPSS rescore
  9. 2026-08-23 16:32 UTCEG score recompute
  10. 2026-08-23 16:32 UTCGHSA enrichment
  11. 2026-08-21 23:45 UTCEPSS rescore
  12. 2026-08-21 21:34 UTCEG score recompute
  13. 2026-08-21 21:34 UTCGHSA enrichment
  14. 2026-08-20 22:51 UTCEPSS rescore
  15. 2026-08-20 18:26 UTCEG score recompute
  16. 2026-08-20 18:26 UTCGHSA enrichment
  17. 2026-08-19 17:00 UTCEPSS rescore
  18. 2026-08-18 13:44 UTCEPSS rescore
  19. 2026-08-17 13:43 UTCEPSS rescore
  20. 2026-08-17 09:38 UTCGHSA enrichment
  21. 2026-08-16 16:45 UTCEG score recompute
  22. 2026-08-16 16:45 UTCGHSA enrichment
  23. 2026-08-16 14:51 UTCEPSS rescore
  24. 2026-08-16 03:12 UTCEG score recompute
  25. 2026-08-16 03:12 UTCGHSA enrichment
Show 75 more
  1. 2026-08-16 02:10 UTCEPSS rescore
  2. 2026-08-15 03:01 UTCEG score recompute
  3. 2026-08-15 03:01 UTCGHSA enrichment
  4. 2026-08-15 01:26 UTCEPSS rescore
  5. 2026-08-14 14:23 UTCGHSA enrichment
  6. 2026-08-14 01:47 UTCEG score recompute
  7. 2026-08-14 01:47 UTCGHSA enrichment
  8. 2026-08-13 21:56 UTCEPSS rescore
  9. 2026-08-13 03:31 UTCGHSA enrichment
  10. 2026-08-12 14:55 UTCEG score recompute
  11. 2026-08-12 14:55 UTCGHSA enrichment
  12. 2026-08-12 13:46 UTCEPSS rescore
  13. 2026-08-12 02:19 UTCGHSA enrichment
  14. 2026-08-11 13:43 UTCEG score recompute
  15. 2026-08-11 13:43 UTCGHSA enrichment
  16. 2026-08-11 00:25 UTCEG score recompute
  17. 2026-08-11 00:25 UTCGHSA enrichment
  18. 2026-08-10 01:45 UTCEG score recompute
  19. 2026-08-10 01:45 UTCGHSA enrichment
  20. 2026-08-09 13:43 UTCEPSS rescore
  21. 2026-08-09 13:09 UTCGHSA enrichment
  22. 2026-08-09 00:33 UTCEG score recompute
  23. 2026-08-09 00:33 UTCGHSA enrichment
  24. 2026-08-08 16:32 UTCEPSS rescore
  25. 2026-08-08 01:57 UTCEG score recompute
  26. 2026-08-08 01:57 UTCGHSA enrichment
  27. 2026-08-07 16:23 UTCEPSS rescore
  28. 2026-08-07 13:20 UTCGHSA enrichment
  29. 2026-08-07 00:44 UTCEG score recompute
  30. 2026-08-07 00:44 UTCGHSA enrichment
  31. 2026-08-06 13:42 UTCEPSS rescore
  32. 2026-08-06 09:50 UTCGHSA enrichment
  33. 2026-08-05 21:07 UTCEG score recompute
  34. 2026-08-05 21:07 UTCGHSA enrichment
  35. 2026-08-05 19:13 UTCEPSS rescore
  36. 2026-08-04 15:05 UTCEPSS rescore
  37. 2026-08-04 05:23 UTCGHSA enrichment
  38. 2026-08-03 16:44 UTCGHSA enrichment
  39. 2026-08-02 18:06 UTCGHSA enrichment
  40. 2026-08-02 05:29 UTCEG score recompute
  41. 2026-08-02 05:29 UTCGHSA enrichment
  42. 2026-08-02 02:23 UTCEPSS rescore
  43. 2026-08-01 16:53 UTCEG score recompute
  44. 2026-08-01 16:53 UTCGHSA enrichment
  45. 2026-08-01 04:12 UTCEPSS rescore
  46. 2026-07-30 16:24 UTCEPSS rescore
  47. 2026-07-30 01:27 UTCEPSS rescore
  48. 2026-07-29 17:12 UTCEG score recompute
  49. 2026-07-29 17:12 UTCGHSA enrichment
  50. 2026-07-28 15:32 UTCEPSS rescore
  51. 2026-07-26 14:51 UTCEPSS rescore
  52. 2026-07-26 14:51 UTCEPSS rescore
  53. 2026-07-26 07:58 UTCEG score recompute
  54. 2026-07-26 07:58 UTCGHSA enrichment
  55. 2026-07-25 14:14 UTCEPSS rescore
  56. 2026-07-24 14:14 UTCEPSS rescore
  57. 2026-07-24 14:14 UTCEPSS rescore
  58. 2026-07-23 14:15 UTCEPSS rescore
  59. 2026-07-23 01:36 UTCEG score recompute
  60. 2026-07-22 22:16 UTCEG score recompute
  61. 2026-07-22 14:05 UTCEPSS rescore
  62. 2026-07-21 15:22 UTCEPSS rescore
  63. 2026-07-20 17:04 UTCEPSS rescore
  64. 2026-07-20 17:04 UTCEPSS rescore
  65. 2026-07-19 02:26 UTCEPSS rescore
  66. 2026-07-19 02:26 UTCEPSS rescore
  67. 2026-07-16 16:59 UTCEPSS rescore
  68. 2026-07-16 16:59 UTCEPSS rescore
  69. 2026-07-15 16:55 UTCEPSS rescore
  70. 2026-07-15 16:55 UTCEPSS rescore
  71. 2026-07-15 01:56 UTCEPSS rescore
  72. 2026-07-15 01:56 UTCEPSS rescore
  73. 2026-07-13 22:27 UTCEPSS rescore
  74. 2026-07-13 22:26 UTCEPSS rescore
  75. 2026-07-13 06:10 UTCEPSS rescore

Frequently asked(5)

What is CVE-2018-25379?
CVE-2018-25379 is a high vulnerability published on May 25, 2026. Collectric CMU 1.0 contains a boolean-based blind SQL injection vulnerability in the lang parameter that allows unauthenticated attackers to manipulate database queries during authentication. Attackers can inject SQL code through the lang parameter in login requests to extract sensitive information…
When was CVE-2018-25379 disclosed?
CVE-2018-25379 was first published in the National Vulnerability Database on May 25, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-25379 actively exploited?
CVE-2018-25379 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.8% of all scored CVEs.
What is the CVSS score of CVE-2018-25379?
CVE-2018-25379 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2018-25379?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-25379, 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-2018-25379

Explore →

Is Your Infrastructure Affected by CVE-2018-25379?

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