Skip to main content

Online Hospital Management System CVE-2026-10208

| EUVDEUVD-2026-33529 MEDIUM
SQL Injection (CWE-89)
2026-06-01 VulDB GHSA-6362-h33q-vf9h
5.5
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Discover exposed login_1.php endpoint
  2. Delivery
    Craft malicious Username SQL payload
  3. Exploit
    Submit POST to login_user function
  4. Execution
    Trigger SQL injection in backend query
  5. Persist
    Bypass authentication or exfiltrate database contents
  6. Impact
    Access patient records and credentials

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

No special conditions - remote unauthenticated exploitation against default configurations of code-projects Online Hospital Management System. The attacker only needs network reachability to the login_1.php endpoint and the ability to submit a Username parameter to the login_user function; no valid credentials, user interaction, or non-default settings are required (CVSS PR:N/UI:N/AC:L). Limiting factors: the application is a niche PHP project typically deployed in academic or small-clinic environments rather than large hospital networks, and the MySQL backend must not be fronted by a WAF or query-sanitizing middleware. Successful data extraction beyond auth bypass also requires the database account used by the app to have read access to the targeted tables.

Impact

The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N indicates the flaw is network-reachable, low-complexity, and requires no privileges or user interaction - classic conditions for opportunistic mass exploitation. However, the C:L/I:L/A:L impact scoring is low for each dimension, yielding an overall 7.3 (High but not Critical); the Exploit Code Maturity (E:P) and Report Confidence (RC:R) qualifiers indicate a proof-of-concept exists and the report is reasonable rather than fully confirmed. EPSS score, KEV status, and SSVC decision values were not provided in the input, so automated-exploitation probability cannot be quantified. Real-world risk depends heavily on exposure: code-projects software is typically used in academic, training, or small-clinic contexts rather than enterprise production, so blast radius is usually narrow, but any internet-exposed instance should be treated as imminently exploitable given the public PoC.

Exploit ScenarioDerived

An unauthenticated attacker discovers a publicly exposed Online Hospital Management System login page via Shodan or Google dorking and submits a crafted POST request to login_1.php with a malicious Username payload such as ' OR 1=1-- to bypass authentication or extract patient records via UNION-based injection. Using the publicly available PoC at github.com/Mi0uno/Online-Hospital-Management-System-has-SQL-Injection, the attacker enumerates the database, exfiltrates PHI/PII, and potentially escalates to writing a webshell via INTO OUTFILE if MySQL file privileges permit.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 01, 2026

SQL injection in code-projects Online Hospital Management System 1.php enables remote unauthenticated attackers to manipulate the Username parameter sent to the login_user function in login_1.php, allowing arbitrary SQL query execution against the backend database. Publicly available exploit code exists (published on GitHub by researcher Mi0uno), increasing the likelihood of opportunistic exploitation, though the CVE is not listed in CISA KEV and EPSS data is not provided. Per CVSS, exploitation requires no authentication or user interaction and impacts confidentiality, integrity, and availability at a low level (CVSS 7.3).

RemediationAI

No vendor-released patch identified at time of analysis - code-projects has not published an advisory or fixed release in the supplied references. As compensating controls, replace the vulnerable SQL in login_1.php's login_user function with prepared statements using PDO or mysqli parameter binding (this is the only durable fix and has no functional side effects). If source-level changes are not feasible immediately, restrict access to the application using network ACLs, VPN, or IP allowlisting so the login page is unreachable from the public internet; this breaks remote workflows for legitimate users and so is only a stopgap. Deploying a WAF with SQLi signatures in front of login_1.php (e.g., ModSecurity with OWASP CRS) can blunt the published PoC but is bypassable by skilled attackers. Monitor https://vuldb.com/vuln/367487 and https://code-projects.org/ for an upstream fix, and review database query logs for anomalous Username payloads (quotes, UNION, comment sequences).

Affected VersionsENISA

Online Hospital Management System 1.php

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in a PHP-based hospital management application authored by code-projects, distributed via code-projects.org. The root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), where the login_user function in login_1.php concatenates or otherwise unsafely incorporates the Username request parameter directly into a SQL statement rather than using parameterized queries or prepared statements. The affected CPE is cpe:2.3:a:code-projects:online_hospital_management_system, which is a freely distributed PHP/MySQL learning/demo project commonly deployed on LAMP stacks. Because the flaw is in the login flow itself, it is reachable pre-authentication on any exposed instance.

Know when Online Hospital Management System gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 5.5 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Primary rating from Vendor (VulDB) · only source for this CVE.

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Severity Changed
Jun 01, 2026 - 02:22 NVD
HIGH MEDIUM
CVSS changed
Jun 01, 2026 - 02:22 NVD
7.3 (HIGH) 5.5 (MEDIUM)

DescriptionCVE.org

A flaw has been found in code-projects Online Hospital Management System 1.php. This impacts the function login_user of the file login_1.php. Executing a manipulation of the argument Username can lead to sql injection. The attack can be executed remotely. The exploit has been published and may be used.

Executive ViewAI

Why It Matters

code-projects Online Hospital Management System contains a critical SQL injection vulnerability (CVE-2026-10208) in its login authentication function that allows unauthenticated attackers to execute arbitrary database queries. Publicly available exploit code on GitHub significantly elevates the risk of immediate attacks against healthcare organizations. Organizations using this system face potential exposure of sensitive patient medical records, unauthorized data manipulation, and clinical system downtime.

Business Impact: High
Compensating Controls

Interim mitigations: (1) Deploy WAF rules to filter SQL injection patterns on login requests; (2) Implement strict input validation and sanitization on Username parameter; (3) Configure database user accounts with minimal required privileges; (4) Enable comprehensive SQL query logging and real-time alerting on anomalous queries; (5) Enforce network segmentation to restrict database access; (6) Suppress verbose SQL error messages from application responses. No vendor-released patch identified at time of analysis; monitor vendor advisory for patch release.

Threat Intelligence Overview

EPSS Score
0.0%
Top 90% exploitable
Exploit
POC
Public exploit code exists
Social Media
1
Sightings
Data Quality
8 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

48
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

Related Vulnerabilities in Online Hospital Management System SQL Injection

View all 2
CVE-2023-37069 CRITICAL POC
9.8 Aug 10

Code-Projects Online Hospital Management System V1.0 is vulnerable to SQL Injection (SQLI) attacks, which allow an attac

CVE-2023-4185 CRITICAL POC
9.8 Aug 06

A vulnerability was found in SourceCodester Online Hospital Management System 1.0. Rated critical severity (CVSS 9.8), t

CVE-2025-5604 HIGH POC
7.3 Jun 04

Critical SQL injection vulnerability in Campcodes Hospital Management System version 1.0, specifically in the /user-logi

CVE-2025-5603 HIGH POC
7.3 Jun 04

Critical SQL injection vulnerability in Campcodes Hospital Management System version 1.0, affecting the /registration.ph

CVE-2025-5602 HIGH POC
7.3 Jun 04

Critical SQL injection vulnerability in Campcodes Hospital Management System version 1.0 affecting the /admin/registrati

CVE-2024-5362 MEDIUM POC
6.9 May 26

A vulnerability classified as critical has been found in SourceCodester Online Hospital Management System 1.0. Rated med

CVE-2025-6408 MEDIUM POC
5.5 Jun 21

A critical SQL injection vulnerability exists in Campcodes Online Hospital Management System version 1.0 affecting the /

CVE-2025-6407 MEDIUM POC
5.5 Jun 21

A SQL injection vulnerability (CVSS 7.3). Risk factors: public PoC available.

CVE-2025-6406 MEDIUM POC
5.5 Jun 21

CVE-2025-6406 is a critical SQL injection vulnerability in Campcodes Online Hospital Management System version 1.0, spec

CVE-2026-7632 MEDIUM POC
5.5 May 02

SQL injection in code-projects Online Hospital Management System 1.0 allows remote unauthenticated attackers to manipula

CVE-2026-7631 LOW POC
2.1 May 02

Improper authorization in code-projects Online Hospital Management System 1.0 allows authenticated remote attackers to m

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy