dbcve.org
Online Hospital Management SystemApplication · Campcodes

CVE-2025-5208

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-26
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 SourceCodester Online Hospital Management System 1.0. This affects an unknown part of the file /admin/check_availability.php. The manipulation of the argument emailid leads to sql injection. It is possible to initiate 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 · high confidence

SQL injection vulnerability in SourceCodester Online Hospital Management System 1.0 at /admin/check_availability.php. The emailid parameter is not properly sanitized, allowing unauthenticated remote attackers to inject arbitrary SQL commands. The critical CVSS score of 9.8 reflects the ease of exploitation and potential for full database compromise including patient records.

MitigationReplace dynamic SQL queries with parameterized statements/prepared statements in check_availability.php. Audit all other PHP files for similar injection vulnerabilities. Apply input validation and output encoding as defense-in-depth.

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. Locate the vulnerable PHP file
    Search the web root directory for the file /admin/check_availability.php. This file is part of the Online Hospital Management System application.
    Affected if The file exists at /admin/check_availability.php and the application is version 1.0
  2. Identify the application version
    Check any version files (VERSION.txt, version.php) in the application root, or inspect the source code for a version variable. Compare against the affected version 1.0.
    Affected if The installed version is 1.0 of Campcodes/SourceCodester Online Hospital Management System
  3. Inspect the vulnerable parameter
    Open /admin/check_availability.php in a text editor and locate the 'emailid' parameter handling. Look for dynamic SQL queries that incorporate this parameter without sanitization or prepared statements.
    Affected if The code contains unsanitized SQL queries using the emailid parameter, directly embedding user input into the query string
  4. Verify the endpoint is accessible
    Confirm the /admin/check_availability.php endpoint is reachable via HTTP/HTTPS without authentication. Attempt a test request with a benign emailid value.
    Affected if The endpoint accepts requests without requiring authentication and processes the emailid parameter
  5. Check for SQL injection vulnerability
    Send a test payload with SQL syntax in the emailid parameter (e.g., emailid=test' OR '1'='1). Observe if the application returns SQL errors or behaves unexpectedly.
    Affected if The application returns SQL database errors or exhibits unexpected behavior indicating SQL injection is possible

Your environment is affected if you have the Online Hospital Management System version 1.0 installed with the /admin/check_availability.php file present and the emailid parameter handled via unsanitized dynamic SQL 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

Replace dynamic SQL queries with parameterized statements/prepared statements in check_availability.php. Audit all other PHP files for similar injection vulnerabilities. Apply input validation and output encoding as defense-in-depth.

Fix this in Online Hospital Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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