dbcve.org
Hospital Management SystemApplication · Code Projects

CVE-2025-8955

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability has been found in PHPGurukul Hospital Management System 4.0. This vulnerability affects unknown code of the file /admin/edit-doctor.php. The manipulation of the argument docfees 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 · high confidence

SQL injection vulnerability in PHPGurukul Hospital Management System 4.0 allows remote attackers to inject malicious SQL commands via the docfees parameter in /admin/edit-doctor.php. The lack of proper input sanitization or parameterized queries enables attackers to manipulate database queries, potentially leading to data exfiltration, modification, or complete system compromise.

MitigationImplement prepared statements/parameterized queries for all database operations in edit-doctor.php, particularly for the docfees parameter. Apply input validation and output encoding as defense-in-depth measures.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hospital Management SystemApplication
Affected:= 4.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Hospital Management System installation
    Identify if PHPGurukul Hospital Management System or Code Projects Hospital Management System is installed in your environment. Check for the presence of PHP application files, typically in the web server document root.
    Affected if The application is installed and accessible on the server
  2. Locate the affected PHP file
    Verify the existence of /admin/edit-doctor.php in the web application directory. This file is the specific component mentioned in the CVE as containing the vulnerability.
    Affected if The file /admin/edit-doctor.php exists in the application
  3. Check admin interface accessibility
    Determine if the /admin/ interface is accessible to remote users or internal network users. This is required for exploitation of the SQL injection.
    Affected if The admin interface is network-accessible to untrusted users
  4. Confirm the application version
    Identify the installed version of the Hospital Management System. Check version files, metadata, or the admin dashboard for version information. Compare against the affected version: 4.0
    Affected if The installed version is exactly 4.0 (Code Projects variant)
  5. Inspect docfees parameter handling
    Review the code in /admin/edit-doctor.php to determine if the docfees parameter is used directly in SQL queries without proper sanitization, prepared statements, or parameterized queries.
    Affected if The docfees parameter is used in dynamic SQL queries without input sanitization or prepared statements

A user is affected if they have Code Projects Hospital Management System version 4.0 installed with the /admin/edit-doctor.php file accessible and the docfees parameter handled without parameterized queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for all database operations in edit-doctor.php, particularly for the docfees parameter. Apply input validation and output encoding as defense-in-depth measures.

Fix this in Hospital Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8955 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8955 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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