/

CVE-2026-90789

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Leave Management login.php

CVE-2026-90789

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Unauthorized database access and data manipulation

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_email input handled by login.php in itsourcecode Leave Management System 1.0. A remote attacker may be able to manipulate database queries when the application processes insufficiently protected input, potentially exposing or altering application data.

Affected context

The issue occurs in the login functionality of itsourcecode Leave Management System 1.0 when the user_email request parameter is incorporated into database processing without adequate separation between user data and SQL commands. Risk is greatest when the login endpoint is remotely reachable and the application account has broad database permissions.

Exploit preconditions

  • Attack surface: The remotely accessible /login.php endpoint
  • Required access: Ability to send requests to the login functionality; valid credentials may not be required
  • Trigger point: Processing of the user_email argument
  • Why exploitation is possible: Input may influence SQL statement structure rather than being treated strictly as data

Why this happens

The underlying bug is an injection flaw in which externally controlled input is incorporated into database queries without reliable parameterization or equivalent query separation. This behavior maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command, with CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component describing the broader injection pattern.

Potential impact

  • An attacker may bypass intended authentication logic
  • Sensitive employee or leave-management records could be disclosed
  • Database records could be modified or deleted
  • The application could experience data integrity loss or service disruption
  • Exposed database privileges could increase downstream compromise risk

General mitigation guidance

Mitigation generally focuses on ensuring that user-controlled values cannot alter SQL command structure.

Common defensive patterns include:

  • Using parameterized queries or prepared statements for all database operations
  • Applying allowlist-based validation appropriate to email input
  • Avoiding dynamic SQL construction from request parameters
  • Returning generic authentication errors and limiting database error exposure
  • Running the application with a narrowly scoped database account
  • Applying least-privilege controls to database schemas and service identities

How teams detect issues like this

Organizations commonly identify SQL injection risks through:

  • Static analysis rules for string concatenation or interpolation in SQL statements
  • Code review checks for unparameterized database queries
  • Dynamic testing of remotely reachable parameters using controlled security test inputs
  • Web application firewall or API policy rules for anomalous query-manipulation patterns
  • Monitoring for unusual authentication failures, database errors, and unexpected query behavior
  • Automated code review tools that flag injection-prone data flows

Sources

SourceLink
github.comgithub.com/Relax-1626/submit/issues/1
itsourcecode.comitsourcecode.com/
vuldb.comvuldb.com/cve/CVE-2026-90789
vuldb.comvuldb.com/submit/919538
vuldb.comvuldb.com/vuln/403295
vuldb.comvuldb.com/vuln/403295/cti

Frequently asked

questions

Yes. The affected login endpoint is described as remotely reachable, so an attacker may be able to submit crafted input over the application interface.

Not necessarily. The primary requirement is access to the login endpoint and an input path that reaches the vulnerable database operation.

Use parameterized queries or prepared statements, validate the input according to its expected format, and ensure database errors are not exposed to clients.

Combine secure query APIs, code review and static analysis, least-privilege database accounts, centralized input-handling policies, and regular security testing of externally accessible endpoints.

Find out what's already
exploitable in your codebase.