CVE-2026-15536
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 vulnerability was identified in itsourcecode Hospital Management System 1.0. This affects an unknown part of the file /patviewprescription.php. The manipulation of the argument delid leads to sql injection. Remote exploitation of the attack is possible. The exploit is publicly available and might be used.
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 · moderate confidenceSQL injection vulnerability in itsourcecode Hospital Management System 1.0 in the /patviewprescription.php file. The 'delid' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 Hospital Management System installationLocate the application files in your webroot and check for version identifiers in README, about page, or composer.json files. Search for 'itsourcecode' or 'Hospital Management' in source code comments and headers.Affected if The installed application is itsourcecode Hospital Management System version 1.0 or an unmodified version of this specific product.
-
Verify patviewprescription.php existsSearch your web directory for the file patviewprescription.php. Common paths may include /patient/, /php/, or the main application directory.Affected if The file patviewprescription.php exists in your deployment and is accessible via the web server.
-
Inspect the delid parameter handlingOpen patviewprescription.php and locate the code handling the 'delid' parameter. Look for SQL queries that directly incorporate this parameter without using prepared statements, parameterized queries, or input sanitization functions like mysqli_real_escape_string or PDO::prepare.Affected if The 'delid' parameter is used in SQL queries without prepared statements, binding, or escaping functions.
-
Test for direct SQL injection vulnerabilityIf the application is live or in a testing environment, send a crafted request to patviewprescription.php with a test value in the 'delid' parameter such as '1' OR '1'='1 to observe if the application returns unexpected data or SQL errors.Affected if The application executes or leaks information from the injected SQL payload, indicating unsanitized input is being processed.
-
Check database user privilegesReview the database configuration file (often config.php, db.php, or similar in the application root) to determine the privileges granted to the application's database user.Affected if The database user has privileges beyond SELECT, INSERT, UPDATE, and DELETE for the specific application database, such as DROP, CREATE, or administrative privileges.
You are affected if you run itsourcecode Hospital Management System 1.0 and the patviewprescription.php file contains direct SQL query construction using the 'delid' parameter without parameterized queries or input sanitization.
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 parameterized queries (prepared statements) for the delid parameter in patviewprescription.php, or implement proper input validation and sanitization. Apply principle of least privilege to the database user.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15536 — 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-15536 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