dbcve.org
Online Hospital Management SystemApplication · Campcodes

CVE-2025-5362

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-30
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, was found in Campcodes Online Hospital Management System 1.0. Affected is an unknown function of the file /admin/doctor-specilization.php. The manipulation of the argument doctorspecilization leads to sql injection. It is possible to launch the attack 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 confidence

A SQL injection vulnerability exists in the Campcodes Online Hospital Management System 1.0 in the /admin/doctor-specilization.php file. The doctorspecilization parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands.

MitigationImplement prepared statements/parameterized queries for all database interactions involving user input. Additionally, apply input validation and output encoding. Consider restricting access to admin panel endpoints or implementing additional access controls.

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. Verify the application is Campcodes Online Hospital Management System
    Check your web server for files matching 'hospital' or 'ohms' in the directory structure. Look for identifying files like README, LICENSE, or the main index.php that may indicate the product name and version.
    Affected if The installed application is Campcodes Online Hospital Management System version 1.0
  2. Confirm the vulnerable file exists
    Locate the file /admin/doctor-specilization.php in your web server document root. This file is typically found in the admin directory of the application.
    Affected if The file /admin/doctor-specilization.php exists and is accessible via the web server
  3. Check if admin interface is accessible
    Attempt to access the admin login page or the doctor-specilization.php file via HTTP/HTTPS to confirm the endpoint is reachable without authentication or with valid admin credentials.
    Affected if The /admin/doctor-specilization.php endpoint responds and accepts input through the doctorspecilization parameter
  4. Review the source code for unsanitized SQL parameter usage
    Open /admin/doctor-specilization.php and search for the doctorspecilization parameter. Examine how it is used in SQL queries - look for direct insertion into query strings without using prepared statements, parameterized queries, or proper escaping functions.
    Affected if The code contains SQL queries that incorporate the doctorspecilization parameter directly without using prepared statements or sanitization functions

Your environment is affected if you are running Campcodes Online Hospital Management System version 1.0 and the /admin/doctor-specilization.php file contains unsanitized SQL queries using the doctorspecilization parameter.

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 interactions involving user input. Additionally, apply input validation and output encoding. Consider restricting access to admin panel endpoints or implementing additional access controls.

Fix this in Online Hospital Management System Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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