dbcve.org
Online Hospital Management SystemApplication · Campcodes

CVE-2025-6406

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-21
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, which was classified as critical, has been found in Campcodes Online Hospital Management System 1.0. Affected by this issue is some unknown functionality of the file /hms/forgot-password.php. The manipulation of the argument fullname leads to sql injection. The attack may be launched 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

A critical SQL injection vulnerability exists in the forgot-password.php file of Campcodes Online Hospital Management System 1.0. The 'fullname' parameter is not properly sanitized before being used in SQL queries, allowing an attacker to inject arbitrary SQL commands. This can lead to unauthorized database access, data exfiltration, or potential authentication bypass.

MitigationImmediately implement prepared statements/parameterized queries for all database operations in forgot-password.php, especially on the fullname parameter. Additionally, apply input validation and consider deploying a WAF rule as a temporary compensating control while the code fix is being deployed.

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
Online Hospital Management SystemApplication
Affected:= 1.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. Identify if Campcodes Online Hospital Management System is installed
    Search the web root directory for the presence of hospital management system files, or check for the application's login page (typically login.php). Look for files with 'hospital', 'clinic', or 'campcodes' in the path.
    Affected if The application is found on the server and is accessible via web browser.
  2. Verify the exact version number
    Check the application version by examining source files, readme files, or any version metadata within the web root. Alternatively, access the login page and look for version information in the footer or page source.
    Affected if The installed version is exactly 1.0.
  3. Confirm the forgot-password.php file exists
    Locate the forgot-password.php file in the web root directory, typically found in the main application directory or an 'admin' subdirectory.
    Affected if The file forgot-password.php exists in the application directory structure.
  4. Inspect the fullname parameter handling
    Examine the forgot-password.php source code to see if the 'fullname' parameter is used directly in SQL queries without prepared statements, parameter binding, or input sanitization functions.
    Affected if The code contains direct SQL query construction using the fullname parameter without prepared statements or proper escaping.

A system is affected if it runs Campcodes Online Hospital Management System version 1.0 and contains the forgot-password.php file where the fullname parameter is handled in SQL queries 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately implement prepared statements/parameterized queries for all database operations in forgot-password.php, especially on the fullname parameter. Additionally, apply input validation and consider deploying a WAF rule as a temporary compensating control while the code fix is being deployed.

Recommended fix Moderate confidence
  1. Do not expose the /hms/forgot-password.php endpoint to untrusted networks until a vendor patch is available
  2. If possible, implement input validation and sanitization on the fullname parameter as a temporary mitigation
  3. Apply a WAF rule to detect and block SQL injection attempts targeting the forgot-password.php endpoint
  4. Contact Campcodes directly to inquire about the availability of a patched version or hotfix for this SQL injection vulnerability
  5. Restrict network access to the hospital management system to trusted users only to reduce attack surface
Caveat No fixed version information available in the CVE description; contact vendor for patch availability

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Online Hospital Management System Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6406 — 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-6406 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