/

CVE-2026-75089

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in PHPGurukul Complaint System

CVE-2026-75089

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

PHPGurukul Complaint Management System 1.0 contains a SQL injection weakness in the email handling logic of user/check_availability.php. A remote attacker may be able to manipulate database queries, potentially accessing or altering data when the affected endpoint is reachable and input is insufficiently protected.

Affected context

The issue occurs in the user availability-checking functionality exposed through user/check_availability.php. Deployments may be at risk when the endpoint accepts email input from remote clients and incorporates that input into database queries without effective parameterization, validation, or equivalent query boundary controls.

Exploit preconditions

  • Attack surface: The remotely reachable user/check_availability.php endpoint
  • Required access: Network access to the affected web application; authentication may not be required
  • Trigger point: Processing of the email argument during availability checking
  • Why exploitation is possible: User-controlled input may influence database query construction without reliable separation between data and SQL instructions

Why this happens

The underlying bug is an injection flaw in which externally supplied email data can affect the structure or meaning of a database query. This behavior maps to CWE-89, SQL Injection, and is also related to CWE-74, because input is interpreted as part of a command or query language rather than being handled strictly as data. The insecure pattern is dynamic query construction using untrusted input without a safe parameter-binding boundary.

Potential impact

  • An attacker may read sensitive records from the application database.
  • An attacker could modify, delete, or corrupt complaint-management data.
  • The vulnerability may enable authentication or authorization data exposure.
  • Database availability could be affected through resource-intensive queries.
  • Information obtained from the database may support further attacks.

General mitigation guidance

Mitigation generally centers on ensuring that all database operations treat

request values as data rather than executable query syntax.

Common defensive patterns include:

  • Use parameterized queries or prepared statements for every database operation.
  • Apply allowlisted validation appropriate to email fields as an additional control.
  • Avoid assembling SQL statements through string concatenation or interpolation.
  • Use database accounts with only the permissions required by the endpoint.
  • Return generic errors and avoid exposing database details to clients.
  • Centralize data-access controls and enforce secure defaults across endpoints.
  • Reduce input trust by validating at boundaries while retaining parameter binding

as the primary protection.

How teams detect issues like this

Detection approaches may include:

  • Static analysis for SQL construction that concatenates request parameters.
  • Code review checks for direct use of email or other request values in query strings.
  • Dynamic testing with safely controlled injection-oriented test cases in non-production environments.
  • Web-application firewall or policy monitoring for anomalous query-like input.
  • Database auditing for unexpected query patterns, errors, access volumes, or writes.
  • Automated security review tools can help identify unsafe data-access patterns,

but findings should be confirmed against the application's query behavior.

Sources

SourceLink
github.comgithub.com/niaoniaollll/cve/issues/3
phpgurukul.comphpgurukul.com/
vuldb.comvuldb.com/cve/CVE-2026-75089
vuldb.comvuldb.com/submit/876776
vuldb.comvuldb.com/vuln/391316
vuldb.comvuldb.com/vuln/391316/cti

Frequently asked

questions

Yes. The affected functionality is described as remotely reachable, although

practical exploitation depends on network exposure and any authentication or

access controls protecting the endpoint.

An attacker generally needs the ability to submit requests to the availability

checking function. Whether authentication is required depends on the deployment

and route configuration.

Use parameterized queries or prepared statements, validate the expected email

format, and ensure database errors are not returned to users.

Enforce secure data-access abstractions, review all request-to-query data flows,

apply least-privilege database accounts, and include static and dynamic security

testing in the development lifecycle.

Find out what's already
exploitable in your codebase.