CVE-2026-36388
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 · uneditedA Cross-Site Scripting (XSS) vulnerability was found in PHPGurukal Hospital Management System v4.0 in the /hospital/hms/edit-profile.php page. This flaw allows an authenticated attacker (patient) to inject a malicious script payload into the User Name parameter, which is stored in the application and later rendered in the doctor s interface.
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability in PHPGurukal Hospital Management System v4.0 allows authenticated patients to inject malicious JavaScript into the User Name parameter on the /hospital/hms/edit-profile.php page. The payload is stored in the database and executes when rendered in the doctor's interface.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm PHPGurukal HMS v4.0 installationLocate the application by searching for files containing 'PHPGurukul' or 'Hospital Management System'. Check version.php, readme.txt, or source code headers for version number v4.0.Affected if The application is installed and the version is 4.0 exactly or falls within the v4.0 release line.
-
Verify edit-profile.php existsCheck for the presence of the file at /hospital/hms/edit-profile.php or search the web root for edit-profile.php.Affected if The file /hospital/hms/edit-profile.php exists and is accessible via the web server.
-
Identify if User Name field accepts inputLog in as a patient user and navigate to the profile editing page. Locate the User Name input field and verify it accepts and stores arbitrary text input.Affected if The User Name field on edit-profile.php accepts and stores unsanitized input.
-
Inspect database for stored XSS payloadsQuery the database table that stores user profile information (typically a table named users, patient_profile, or similar). Search for HTML script tags or JavaScript event handlers in the User Name column.Affected if The database contains stored JavaScript or HTML in user name fields that was not properly encoded on storage.
The environment is affected if PHPGurukal Hospital Management System v4.0 is installed, the edit-profile.php file exists, and the User Name field stores unsanitized input that can be retrieved and rendered unescaped in the doctor's interface.
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 dataImplement input validation to sanitize the User Name parameter on submission, and apply context-aware output encoding when displaying user data to prevent script execution.
- 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-36388 — 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-36388 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