dbcve.org
Online Hospital Management SystemApplication · Campcodes

CVE-2025-5229

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-27
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 was found in Campcodes Online Hospital Management System 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file /admin/view-patient.php. The manipulation of the argument viewid 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

SQL injection vulnerability in Campcodes Online Hospital Management System 1.0 allows remote attackers to inject malicious SQL queries via the 'viewid' parameter in /admin/view-patient.php. The lack of proper input sanitization or parameterized queries enables attackers to manipulate database queries, potentially exposing sensitive patient data or compromising the entire database.

MitigationImmediate remediation requires replacing dynamic SQL queries with prepared statements/parameterized queries in view-patient.php, implementing proper input validation, and applying output encoding. Given the public exploit availability and critical CVSS score, this should be treated as an emergency fix with immediate deployment.

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. Confirm the installed application is Campcodes Hospital Management System
    Inspect the web application to identify its product name. Check the application UI, footer, source code, or installation files for the product name 'Campcodes Online Hospital Management System'.
    Affected if The installed application is not Campcodes Online Hospital Management System
  2. Verify the application version is 1.0
    Locate the version number of the installation. Check admin panel about pages, version files in the installation directory, or any version metadata shipped with the software.
    Affected if The installed version is not 1.0
  3. Check if the vulnerable PHP file exists
    Locate the file view-patient.php within the web application's admin directory. This is typically found at /admin/view-patient.php relative to the web document root.
    Affected if The file /admin/view-patient.php does not exist in the installation
  4. Confirm the viewid parameter is processed
    Make an HTTP request to /admin/view-patient.php and observe if the viewid parameter is accepted and used in database queries. A test request with viewid=1 can confirm the parameter is functional.
    Affected if The viewid parameter is not accepted or not processed by the application
  5. Determine network accessibility of the vulnerable endpoint
    Assess whether the /admin/view-patient.php endpoint is accessible from untrusted networks. Check if the admin area is exposed to the internet or accessible without proper network segmentation.
    Affected if The vulnerable endpoint is not network-accessible to remote attackers

A system is affected only if it runs Campcodes Online Hospital Management System version 1.0 with the view-patient.php file present and the viewid parameter accessible to remote attackers.

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

Immediate remediation requires replacing dynamic SQL queries with prepared statements/parameterized queries in view-patient.php, implementing proper input validation, and applying output encoding. Given the public exploit availability and critical CVSS score, this should be treated as an emergency fix with immediate deployment.

Fix this in Online Hospital Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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