SQL Injection vulnerability in damasac thaipalliative_lte through version 3.0 allows remote attackers to execute arbitrary SQL commands via the idFormMain parameter to /substudy/ezform.php (line 14) and the id parameter (line 49). The parameters are concatenated directly into SQL queries without sanitization or parameterized statements.
CVE-2026-38581
CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-11. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EPSS
- 24.8%
- KEV
- Not listed
Published
June 11, 2026
Last Modified
June 11, 2026
Advisory Details (2)
Auto-updated Jun 20, 2026Patch available.
generic Patch Available
advisories/2026/CVE-2026-38581.md at main · theemperorspath/advisories · GitHub
https://github.com/theemperorspath/advisories/blob/main/2026/CVE-2026-38581.mdgeneric
thaipalliative_lte/substudy/ezform.php at 57b57630fb403eba524533062ef5244e9b7c4380 · damasac/thaipalliative_lte · GitHub
https://github.com/damasac/thaipalliative_lte/blob/57b57630fb403eba524533062ef5244e9b7c4380/substudy/ezform.php#L14Vendor Advisories for CVE-2026-38581(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.
Frequently asked(5)
What is CVE-2026-38581?
CVE-2026-38581 is a critical vulnerability published on June 11, 2026. SQL Injection vulnerability in damasac thaipalliative_lte through version 3.0 allows remote attackers to execute arbitrary SQL commands via the idFormMain parameter to /substudy/ezform.php (line 14) and the id parameter (line 49). The parameters are concatenated directly into SQL queries without…
When was CVE-2026-38581 disclosed?
CVE-2026-38581 was first published in the National Vulnerability Database on June 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-38581 actively exploited?
CVE-2026-38581 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-38581?
CVE-2026-38581 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-38581?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-38581, 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-2026-38581
Is Your Infrastructure Affected by CVE-2026-38581?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.