/

CVE-2026-90514

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in School Registration System

CVE-2026-90514

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database compromise, including potential unauthorized data access or modification

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 remotely exploitable SQL injection vulnerability affects the Status argument processed by the School Registration and Fee System's student-saving endpoint. An attacker may manipulate database queries when this input is handled without adequate separation from SQL commands, potentially exposing or altering application data.

Affected context

The vulnerability occurs in SourceCodester School Registration and Fee System 1.0, specifically in the request-handling logic associated with /bilal/normal/save_stud.php. Risk is present when the endpoint accepts the Status argument from a remote client and incorporates it into database operations without effective parameterization or equivalent query controls.

Exploit preconditions

  • Attack surface: A remotely accessible web endpoint
  • Required access: The ability to send requests to the affected student-saving functionality; authentication requirements may depend on deployment configuration
  • Trigger point: Processing of the Status argument by /bilal/normal/save_stud.php
  • Why exploitation is possible: Input may influence SQL query construction without sufficient separation between data and query logic

Why this happens

The underlying bug is an injection flaw in which externally supplied input is allowed to affect SQL statement structure. This behavior maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'). CWE-74 is also relevant as a broader injection category because untrusted data crosses an interpreter boundary without reliable parameterization or context-aware handling.

Potential impact

  • An attacker may read unauthorized records from the application database.
  • An attacker could alter, insert, or delete stored registration and fee data.
  • The application may disclose sensitive student or administrative information.
  • Database integrity and service availability could be degraded.
  • Depending on database privileges, the compromise could affect other application functions.

General mitigation guidance

Mitigation generally focuses on keeping user-controlled values separate from SQL syntax and reducing the trust placed in request parameters.

Common defensive patterns include:

  • Use parameterized queries, prepared statements, or safely managed data-access abstractions.
  • Validate the Status value against an allowlisted set of expected values and enforce its type and length.
  • Avoid constructing SQL statements through string concatenation or interpolation.
  • Apply least-privilege permissions to the application database account.
  • Return generic database errors to clients while recording useful security telemetry internally.
  • Enforce authentication and authorization checks appropriate to the student-record operation.

How teams detect issues like this

Detection approaches commonly include:

  • Static analysis rules for SQL string concatenation, interpolation, and dynamic query construction using request parameters.
  • Code review checks tracing Status and similar inputs from HTTP handlers into database APIs.
  • Dynamic testing with benign boundary and type-variation inputs, without relying on destructive payloads.
  • Web application firewall or API policy rules that identify anomalous database-oriented input patterns.
  • Database monitoring for unexpected query shapes, privilege use, error spikes, or unusual record-access volume.
  • Automated security review tools can help identify unparameterized query paths during development.

Sources

SourceLink
github.comgithub.com/zuojiu567/cve/issues/1
vuldb.comvuldb.com/cve/CVE-2026-90514
vuldb.comvuldb.com/submit/912050
vuldb.comvuldb.com/vuln/403101
vuldb.comvuldb.com/vuln/403101/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes. The reported attack surface is a remotely accessible web endpoint. Whether an attacker must authenticate depends on how the application is deployed and how access to the endpoint is controlled.

An attacker needs the ability to submit a request that reaches the affected student-saving functionality and supplies the Status argument. Network exposure, authentication, and authorization controls determine the practical scope.

The safest pattern is to use parameterized database queries or prepared statements, validate the value against an allowlist, and avoid incorporating request data into SQL syntax.

Combine secure data-access APIs with least-privilege database accounts, focused code review, static analysis, input-flow testing, and monitoring for abnormal database activity.

Find out what's already
exploitable in your codebase.