/

CVE-2026-75778

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Task Management System 1.0

CVE-2026-75778

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database compromise and potential 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 SQL injection vulnerability in the Task Management System login form allows remotely supplied email input to influence database queries. An attacker who can reach the affected endpoint may manipulate query behavior, potentially bypass authentication or access and alter database information.

Affected context

The vulnerability occurs in the Login Form component of Task Management System 1.0, specifically where the email argument is processed by Operation::select_with_multiple_condition in /index.php. Risk is present when externally supplied input is incorporated into SQL statements without effective parameterization or equivalent query-boundary protections.

Exploit preconditions

  • Attack surface: Remotely accessible Login Form endpoint
  • Required access: Ability to submit requests containing an attacker-controlled email value
  • Trigger point: Processing of the email parameter by the affected database query operation
  • Why exploitation is possible: Untrusted input may alter the intended SQL statement when query construction does not properly separate data from executable SQL syntax

Why this happens

The underlying bug is an injection flaw caused by treating user-controlled email data as part of a database command. This 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 is dynamic SQL construction that fails to use parameterized queries, trusted query builders, or equivalent separation between SQL structure and values.

Potential impact

  • An attacker may bypass intended login or authorization checks
  • Sensitive database records could be read or disclosed
  • Database records could be modified or deleted
  • Application availability could be affected through resource-intensive queries
  • Compromised data could enable further attacks against users or connected services

General mitigation guidance

Mitigation generally focuses on ensuring that user-controlled values cannot become executable SQL syntax.

Common defensive patterns include:

  • Use parameterized queries or prepared statements for all database operations
  • Prefer query builders or data-access abstractions that enforce value binding by default
  • Apply allowlist-based input validation appropriate to email fields as a secondary control
  • Use database accounts with only the permissions required by the application
  • Keep authentication and authorization decisions independent of ambiguous query results
  • Avoid exposing detailed database errors to external users
  • Treat client-submitted input as untrusted across every request path

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis rules for string concatenation or interpolation inside SQL execution calls
  • Code review checks for dynamic query construction involving request parameters
  • Runtime application testing using safe injection-detection probes in authorized environments
  • Database and web-application monitoring for anomalous query patterns, repeated authentication failures, and unexpected data access
  • Policy enforcement requiring prepared statements or approved data-access libraries

Automated security review tools may help flag risky query-building patterns, but findings should be validated against actual data-flow and database usage.

Sources

SourceLink
code-projects.orgcode-projects.org/
github.comgithub.com/niaoniaollll/cve/issues/5
vuldb.comvuldb.com/cve/CVE-2026-75778
vuldb.comvuldb.com/submit/877771
vuldb.comvuldb.com/vuln/391521
vuldb.comvuldb.com/vuln/391521/cti

Frequently asked

questions

Yes. The reported attack surface is the remotely reachable Login Form, where an attacker can submit a crafted value for the email parameter.

Not necessarily. Because the affected functionality is part of a login form, exploitation may be possible before authentication if the endpoint is publicly reachable and processes the input.

Use parameterized queries or prepared statements so email values are transmitted as data rather than incorporated into SQL syntax. Strict input validation should supplement, not replace, query parameterization.

Enforce secure database-access patterns through code review, static analysis, approved query libraries, least-privilege database accounts, and authorized security testing of externally supplied inputs.

Find out what's already
exploitable in your codebase.