CVE-2026-6006
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 has been found in code-projects Patient Record Management System 1.0. The impacted element is an unknown function of the file /edit_hpatient.php. The manipulation of the argument ID leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may 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 Patient Record Management System 1.0 allows remote attackers to inject malicious SQL queries via the ID parameter in /edit_hpatient.php, potentially exposing or manipulating sensitive patient data.
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 Patient Record Management System installationLocate the application web root directory and identify if the Patient Record Management System version 1.0 is installed. Check for common paths like /var/www/html/ or C:\inetpub\wwwroot\ and look for application-specific folders or metadata files that indicate the software name and version.Affected if The system has Patient Record Management System version 1.0 installed
-
Verify the vulnerable file existsCheck for the presence of /edit_hpatient.php in the web application directory. This file should exist within the application's PHP source code structure.Affected if The file edit_hpatient.php exists in the web application directory
-
Confirm the ID parameter is acceptedExamine the edit_hpatient.php source code to verify it accepts an ID parameter (typically via GET or POST request). Look for code that retrieves the ID using $_GET['id'] or $_POST['id'].Affected if The file processes an ID parameter from user input
-
Check if dynamic SQL queries are usedReview the edit_hpatient.php code for direct SQL query construction using the ID parameter without prepared statements or parameter binding. Look for patterns like 'SELECT * FROM ... WHERE id=' . $_GET['id'].Affected if SQL queries are constructed dynamically with the ID parameter without parameterized queries
-
Test for SQL injection susceptibilityIf authorized and in a non-production environment, attempt a simple SQL injection test on the ID parameter (e.g., adding a single quote ' or OR 1=1) to the edit_hpatient.php?ID= URL and observe if database errors are returned.Affected if The ID parameter reflects SQL syntax errors or returns unexpected database information
The system is affected if Patient Record Management System 1.0 is installed, the edit_hpatient.php file exists, and it uses dynamic SQL queries with the ID parameter without parameterized queries.
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 dynamic SQL queries with parameterized queries (prepared statements) in /edit_hpatient.php and implement proper input validation on the ID parameter to prevent SQL injection attacks.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6006 — 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-6006 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