CVE-2018-25221

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-03-28. NVD baseline CVSS 9.8; sources differ by 0.0.

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

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

EChat Server 3.1 contains a buffer overflow vulnerability in the chat.ghp endpoint that allows remote attackers to execute arbitrary code by supplying an oversized username parameter. Attackers can send a GET request to chat.ghp with a malicious username value containing shellcode and ROP gadgets to achieve code execution in the application context.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/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
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
55%
KEV
Not listed

Published

March 28, 2026

Last Modified

June 17, 2026

Advisory Details (2)

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

EChat Server 3.1 Buffer Overflow via chat.ghp username Parameter | Advisories | VulnCheck

https://www.vulncheck.com/advisories/echat-server-buffer-overflow-via-chat-ghp-username-parameter
generic🟡 PoC Available

EChat Server 3.1 - 'CHAT.ghp' Buffer Overflow - Windows remote Exploit

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× 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.

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

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

Frequently asked(5)

What is CVE-2018-25221?
CVE-2018-25221 is a critical vulnerability published on March 28, 2026. EChat Server 3.1 contains a buffer overflow vulnerability in the chat.ghp endpoint that allows remote attackers to execute arbitrary code by supplying an oversized username parameter. Attackers can send a GET request to chat.ghp with a malicious username value containing shellcode and ROP gadgets…
When was CVE-2018-25221 disclosed?
CVE-2018-25221 was first published in the National Vulnerability Database on March 28, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-25221 actively exploited?
CVE-2018-25221 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 44.7% of all scored CVEs.
What is the CVSS score of CVE-2018-25221?
CVE-2018-25221 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-25221?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-25221, 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-25221

Explore →

Is Your Infrastructure Affected by CVE-2018-25221?

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