CVE-2019-25538

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-03-12. a secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
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: None knownExposed: 0

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

202CMS v10 beta contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the log_user parameter. Attackers can send crafted requests with malicious SQL statements in the log_user field to extract sensitive database information or modify database contents.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
42(Track)
EG Risk 42/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
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

March 12, 2026

Last Modified

June 17, 2026

Advisory Details (3)

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

202CMS v10 beta SQL Injection via log_user Parameter | Advisories | VulnCheck

https://www.vulncheck.com/advisories/202cms-v10-beta-sql-injection-via-log-user-parameter
generic🟡 PoC Available

202CMS v10beta - Multiple SQL Injection - PHP webapps Exploit

https://www.exploit-db.com/exploits/46579
generic

202CMS download | SourceForge.net

https://sourceforge.net/projects/b202cms/

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2019-25538?
CVE-2019-25538 is a high vulnerability published on March 12, 2026. 202CMS v10 beta contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the loguser parameter. Attackers can send crafted requests with malicious SQL statements in the loguser field to extract sensitive database…
When was CVE-2019-25538 disclosed?
CVE-2019-25538 was first published in the National Vulnerability Database on March 12, 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-2019-25538 actively exploited?
CVE-2019-25538 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 69.7% of all scored CVEs.
What is the CVSS score of CVE-2019-25538?
CVE-2019-25538 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2019-25538?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-25538, 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-25538

Explore →

Is Your Infrastructure Affected by CVE-2019-25538?

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

Start Free Scan →Browse All CVEs