CVE-2026-38581
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSQL 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in damasac thaipalliative_lte v3.0 allows remote attackers to execute arbitrary SQL commands via direct concatenation of the idFormMain and id parameters into SQL queries at /substudy/ezform.php lines 14 and 49. No input sanitization or parameterized queries are used.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm damasac thaipalliative_lte v3.0 installationLocate the application root directory and check for version markers such as version files, README files, or the application footer that displays the version number. Compare the installed version against v3.0.Affected if The installed version is damasac thaipalliative_lte v3.0 or earlier.
-
Locate the vulnerable PHP fileSearch the web root for the file /substudyezform.php or /substudy/ezform.php. Verify its presence in the application directory structure.Affected if The file /substudy/ezform.php exists in the application web root.
-
Check parameter exposure in HTTP requestsExamine application traffic or review the source code of ezform.php to confirm that the idFormMain and id parameters are accepted via GET or POST requests and passed to SQL queries.Affected if The application accepts idFormMain or id parameters without sanitization in HTTP requests to ezform.php.
-
Inspect SQL query construction in ezform.phpReview the source code of ezform.php and search for SQL query strings that concatenate the idFormMain or id variables directly into queries without using prepared statements, parameter binding, or escaping functions.Affected if The code contains SQL queries with direct string concatenation of idFormMain or id variables (e.g., 'SELECT * FROM table WHERE id=' . $id).
A user is affected if they run damasac thaipalliative_lte v3.0 with the /substudy/ezform.php file accessible and the application processes idFormMain or id parameters via unsanitized SQL concatenation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace direct string concatenation with prepared statements/parameterized queries for both idFormMain and id parameters. Validate and whitelist all user inputs before database operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38581 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-38581 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data