CVE-2026-10184
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 security flaw has been discovered in SourceCodester Hospitals Patient Records Management System 1.0. This impacts an unknown function of the file /classes/Users.php?f=delete. The manipulation of the argument ID results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks.
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 SourceCodester Hospitals Patient Records Management System 1.0 allows remote attackers to inject malicious SQL queries via the ID parameter in the /classes/Users.php?f=delete endpoint.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 SourceCodester Hospitals Patient Records Management System is installedLocate the application installation directory and check for typical indicators such as the presence of 'hprms' folder, index.php, or configuration files. Check version.php or README files for version number 1.0Affected if The application is SourceCodester Hospitals Patient Records Management System version 1.0 or another version within this product line
-
Verify the affected Users.php file existsNavigate to the web root and confirm the file /classes/Users.php exists. This is the file containing the vulnerable delete functionAffected if The file /classes/Users.php is present in the application installation
-
Inspect the delete function in Users.php for SQL injection vulnerabilityOpen /classes/Users.php and locate the 'delete' function handling the ID parameter. Look for dynamic SQL query construction where the ID parameter is concatenated directly into the SQL statement without using prepared statements or parameter bindingAffected if The delete function constructs SQL queries by directly inserting the ID parameter into the query string without parameterization
-
Check if the delete endpoint is accessibleConfirm the application routes requests to /classes/Users.php?f=delete. Test if this endpoint responds (without exploiting) by observing the application's routing behavior or accessing the URL with a test ID parameterAffected if The ?f=delete endpoint is reachable and processes the ID parameter
-
Verify lack of input validation on the ID parameterReview the delete function code to determine whether the ID parameter undergoes any sanitization, type casting, or validation before being used in the SQL queryAffected if The ID parameter is used directly in SQL queries without sanitization, validation, or type checking
If SourceCodester Hospitals Patient Records Management System is installed and the /classes/Users.php file contains a delete function that uses the ID parameter in unparameterized SQL queries, the environment is affected by this CVE.
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 for the ID parameter and implement proper input validation to prevent SQL injection attacks.
- Consultation3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10184 — 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-10184 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