CVE-2026-38579
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 · uneditedMultiple reflected Cross-Site Scripting (XSS) vulnerabilities in damasac thaipalliative_lte through version 3.0 allow remote attackers to inject arbitrary web script or HTML via the idFormMain parameter (line 24), the id parameter (lines 25, 75), and the ptid_key parameter (lines 26, 42) in /substudy/ezform.php. User input is echoed into HTML attributes and JavaScript contexts without encoding.
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 confidenceMultiple reflected XSS vulnerabilities exist in damasac thaipalliative_lte version 3.0 where user-supplied input from idFormMain, id, and ptid_key parameters in /substudy/ezform.php is directly echoed into HTML attributes and JavaScript contexts without proper encoding or sanitization. An attacker can craft malicious URLs to inject arbitrary JavaScript that executes in the victim's browser.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Locate the thaipalliative_lte applicationSearch for the application directory on the web server. Look for directories named 'thaipalliative_lte' or 'damasac' in the web root. Common paths include /var/www/html/, /htdocs/, or the web server document root.Affected if The application is not found on the server - the server is not running this software.
-
Check the application versionInspect the application's version file, README, or any version identifier within the thaipalliative_lte directory. Look for a version.php, version.txt, or similar file that displays the version number 3.0.Affected if The installed version is exactly 3.0 or falls within version 3.x range - the vulnerable version is present.
-
Verify the vulnerable file existsCheck for the presence of /substudy/ezform.php within the application directory. Confirm the path is thaipalliative_lte/substudy/ezform.php relative to the web root.Affected if The file /substudy/ezform.php exists - the vulnerable component is present.
-
Confirm parameter usage in the fileReview the source code of ezform.php to verify it processes the idFormMain, id, or ptid_key parameters. Search for occurrences of these parameter names in the file to confirm they are used without sanitization.Affected if The code shows these parameters are accepted and echoed directly into HTML or JavaScript contexts without encoding.
The server is affected if the thaipalliative_lte application version 3.0 is installed and the file /substudy/ezform.php exists with unencoded output of the idFormMain, id, or ptid_key parameters.
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 dataApply context-aware output encoding (HTML entity encoding for attributes, JavaScript escaping for script contexts) to all user-supplied input before echoing it into the page. Implement input validation and Content Security Policy headers as defense-in-depth measures.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38579 — 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-38579 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