/

CVE-2026-76574

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Hospital Information System

CVE-2026-76574

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database Access and Authentication Bypass

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A high-severity SQL injection vulnerability affects the User Login Handler in code-projects Hospital Information System 1.0. A remotely reachable login request may allow an attacker to manipulate the email input and alter database queries, potentially exposing or changing application data.

Affected context

The vulnerability occurs in the User::login function within includes/users/UsersController.php. It becomes risky when the application incorporates the email parameter into database queries without reliably separating user-controlled data from SQL syntax. Deployments that expose the login handler over a network may present a remotely accessible attack surface.

Exploit preconditions

  • Attack surface: The web-accessible user login handler
  • Required access: No prior authenticated access may be necessary if the login endpoint is publicly reachable
  • Trigger point: Processing of the email argument during login
  • Why exploitation is possible: User-controlled input may influence SQL query structure when parameterization or equivalent query controls are absent

Why this happens

The underlying bug is an injection flaw in which externally supplied input is combined with a database query as executable SQL rather than being treated strictly as data. This behavior maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection) and is also related to CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component. The insecure pattern commonly involves dynamic query construction without consistently using parameterized statements or a safe query abstraction.

Potential impact

  • An attacker may bypass intended login controls
  • Sensitive database records could be disclosed
  • Application data could be modified or deleted
  • Database availability could be affected
  • Information obtained from the database could support further attacks

General mitigation guidance

Mitigation generally focuses on ensuring that database commands cannot be altered by untrusted input.

Common defensive patterns include:

  • Using parameterized queries or prepared statements for all user-supplied values
  • Favoring database APIs and query builders that separate parameters from query structure
  • Applying server-side input validation as a supplementary control, not as a replacement for parameterization
  • Restricting the database account to the minimum permissions required by the application
  • Avoiding detailed database errors in responses and enforcing secure authentication behavior
  • Keeping administrative and sensitive database operations separate from ordinary login functionality

How teams detect issues like this

Organizations can look for SQL injection risks through:

  • Static analysis rules identifying string concatenation or interpolation in SQL statements
  • Code review checks for database queries that receive request parameters without bound parameters
  • Dynamic testing of login and other input-handling endpoints using approved security test processes
  • Web application firewall or gateway policies that identify suspicious query-manipulation patterns
  • Database monitoring for unusual authentication queries, error spikes, schema access, or unexpected data changes
  • Automated code review and software composition analysis tools that flag unsafe query construction patterns

Sources

SourceLink
code-projects.orgcode-projects.org/
github.comgithub.com/niaoniaollll/cve/issues/6
vuldb.comvuldb.com/cve/CVE-2026-76574
vuldb.comvuldb.com/submit/877784
vuldb.comvuldb.com/vuln/393038
vuldb.comvuldb.com/vuln/393038/cti

Frequently asked

questions

Yes. The affected login handler is described as remotely reachable, so an attacker may be able to target it over the network when the application is exposed.

Not necessarily. If the login endpoint accepts unauthenticated requests, the key requirement may be network access to that endpoint rather than an existing user account.

Use parameterized queries or prepared statements so the email value is always handled as data, not interpreted as part of SQL syntax.

Combine parameterized database access with secure code review, automated static analysis, least-privilege database accounts, controlled error handling, and security testing of externally supplied inputs.

Find out what's already
exploitable in your codebase.