Severity:

HIGH RISK

(7.3)

SQL Injection in PHPGurukul Online Course Registration

CVE-2026-5813

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Data Exposure and Manipulation via SQL Injection

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 Online Course Registration 3.1 contains a SQL injection vulnerability in /check_availability.php, where the cid parameter is used unsafely in database queries.

A remote attacker can manipulate this parameter to inject SQL fragments, potentially accessing or modifying backend data and influencing application behavior.

Affected context

The vulnerability occurs in the /check_availability.php endpoint of PHPGurukul Online Course Registration 3.1 when handling the cid parameter, typically used to check course or enrollment availability.

It arises in deployments where incoming HTTP request parameters are passed into SQL queries without robust input validation, parameterization, or query abstraction layers.

Any internet-exposed instance relying on a relational database and using this script as part of the registration or course lookup workflow may be affected.

Exploit preconditions

  • Attack surface: HTTP interface to /check_availability.php
  • Required access: Remote, unauthenticated web access to the vulnerable script
  • Trigger point: Supplying crafted values in the cid parameter (e.g., via GET or POST) that flow into SQL statements
  • Why exploitation is possible: The application dynamically interpolates the cid value into SQL queries without using prepared statements or adequate escaping, allowing attacker-controlled input to alter the structure of the executed query.

Why this happens

The core issue maps to CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection').

Application code in /check_availability.php likely constructs SQL queries by concatenating or embedding the cid parameter directly into the query string instead of binding it as a typed parameter.

This pattern treats user-controlled data as trusted SQL syntax, failing to neutralize metacharacters such as quotes, comment markers, or logical operators.

The reference to CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component underscores that the database is a downstream interpreter and the application is not enforcing a clear data-vs-code boundary.

Potential impact

  • Unauthorized reading of database records related to courses, students, or registrations
  • Modification or deletion of course registrations or associated data
  • Bypassing application-level checks that rely on database state
  • Enumeration of database schema, tables, and columns to aid further attacks
  • Potential execution of stacked queries or database-native functions, depending on DBMS configuration

General mitigation guidance

Effective mitigation focuses on strict separation of data and SQL logic:

  • Use parameterized queries or prepared statements for all database access paths involving user input, including cid.
  • Apply server-side validation and normalization to constrain cid to expected formats (e.g., integers or fixed identifiers).
  • Adopt an abstraction layer or ORM that encourages safe query construction and discourages ad-hoc string concatenation.
  • Limit database privileges of the application's account to the minimal set of operations necessary for normal behavior.
  • Centralize database access patterns so that secure-by-default query helpers are reused rather than re-implementing low-level SQL construction.

How teams detect issues like this

Detection can combine code-centric and behavior-centric approaches:

  • Static analysis rules that flag string concatenation involving request parameters (cid) in SQL context within PHP files, especially /check_availability.php.
  • Manual code review focusing on data access layers and any script that builds SQL using $_GET, $_POST, or other user input without parameter binding.
  • Use of interactive application security testing (IAST) or dynamic scanning configured to probe the cid parameter for SQL injection signatures.
  • Logging and monitoring for anomalous SQL patterns (e.g., unexpected operators, comments, or tautological conditions) originating from the check availability endpoint.

Sources

SourceLink
github.comgithub.com/f1rstb100d/CVE/issues/20
phpgurukul.comphpgurukul.com/
vuldb.comvuldb.com/submit/787686
vuldb.comvuldb.com/vuln/356261
vuldb.comvuldb.com/vuln/356261/cti

Frequently asked

questions

Yes. As described, the vulnerable script is reachable over HTTP, and a remote attacker can target the cid parameter without local access.

Typically no. This kind of availability-check endpoint is often exposed without authentication, so an unauthenticated user can send crafted requests if the instance is publicly accessible.

Refactor all queries involving cid (and other user-controlled fields) to use prepared statements or parameterized queries, combined with strict server-side validation of input types and ranges.

Standardize on secure database access APIs, ban ad-hoc string-based SQL construction in coding guidelines, enforce these rules with automated checks in CI, and include regular security reviews of endpoints that process request parameters.

Find out what's already
exploitable in your codebase.