Severity:

HIGH RISK

(7.3)

SQL Injection in Password Parameter of Cyber-III

CVE-2026-5669

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Authentication Bypass and Data Compromise 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

A SQL injection flaw in the password parameter of the /login.php endpoint in Cyber-III Student-Management-System allows user-supplied data to be incorporated directly into database queries.

When an attacker submits crafted input via the Password field, they may be able to manipulate the underlying SQL statement, bypass authentication, and access or modify data remotely.

Affected context

The vulnerability occurs in the login workflow of Cyber-III Student-Management-System, specifically in /login.php where user credentials are processed.

It is present when the application concatenates the Password parameter directly into SQL statements without robust input handling or parameterization.

Deployments exposed to the internet or untrusted networks, and that rely on the affected login endpoint for user authentication, are most at risk.

Exploit preconditions

  • Attack surface: Public or internally exposed web interface at /login.php
  • Required access: Network access to the application; no prior authentication needed
  • Trigger point: Submission of a crafted Password parameter in the login form or equivalent HTTP request
  • Why exploitation is possible: The application appears to embed the raw Password parameter into SQL queries, allowing injection of additional SQL tokens instead of treating user input as a bound value

Why this happens

The underlying bug aligns with CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), and is related to CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component.

The login logic likely constructs SQL statements by string concatenation or interpolation using the Password parameter directly.

Without prepared statements, proper parameter binding, or rigorous escaping, user-controlled input is interpreted as part of the SQL command syntax rather than as data, enabling attackers to alter the intended query behavior.

Potential impact

  • Bypass of authentication controls and unauthorized login as arbitrary users
  • Access to sensitive student or staff records stored in the database
  • Modification or deletion of application data, including academic records
  • Extraction of credential hashes or other secrets from authentication tables
  • Potential pivot to underlying database server features, depending on configuration

General mitigation guidance

Effective mitigation typically focuses on enforcing strict separation between code and data in database operations and reducing trust in all externally supplied input:

  • Use parameterized queries or prepared statements for all database access, especially in authentication logic.
  • Centralize data access through a vetted data access layer that forbids ad-hoc string-built SQL.
  • Apply conservative input validation to authentication fields, checking for expected formats and lengths.
  • Minimize database privileges of the application account to only necessary operations and tables.
  • Consider employing an allowlist-based query construction pattern and avoiding dynamic query fragments where possible.

How teams detect issues like this

Teams can detect this class of issue using a combination of automated and manual approaches:

  • Static analysis rules that flag SQL queries built via string concatenation or interpolation with user-controlled variables.
  • Code review checklists that require verification of prepared statements for all login and authentication-related queries.
  • Runtime monitoring or web application firewalls configured with signatures and heuristics for SQL injection patterns.
  • Security testing (including automated DAST tools) targeted at authentication endpoints to identify anomalous behavior when injecting SQL metacharacters.

Sources

SourceLink
github.comgithub.com/Cyber-III/Student-Management-System/
github.comgithub.com/Cyber-III/Student-Management-System/issues/240
vuldb.comvuldb.com/submit/785942
vuldb.comvuldb.com/vuln/355491
vuldb.comvuldb.com/vuln/355491/cti

Frequently asked

questions

Yes. An attacker with network access to the /login.php endpoint can attempt to exploit the vulnerability by submitting crafted Password values.

No prior authentication is required. The issue resides in the login handler itself, which is typically accessible to unauthenticated users.

Refactor the login code to use parameterized queries or prepared statements exclusively, ensuring that the Password parameter (and all other user inputs) are always bound as data rather than interpolated into SQL strings.

Establish a development standard that forbids string-built SQL, enforce it through code review and static analysis, and design a shared data access layer that encapsulates secure query construction for all database interactions.

Find out what's already
exploitable in your codebase.