/

CVE-2026-90516

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in SourceCodester School Fee System

CVE-2026-90516

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database compromise and unauthorized data access

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 high-severity SQL injection vulnerability affects the period parameter in the School Registration and Fee System 1.0. Because the vulnerable endpoint is remotely accessible, an attacker may manipulate database queries and potentially read, alter, or delete application data.

Affected context

The vulnerability occurs in the payment reporting functionality at /bilal/normal/pay_report.php when the period argument is incorporated into a database query without sufficient separation between data and SQL syntax. It is most relevant where the application is exposed to remote users and the affected parameter is reachable without strong access controls.

Exploit preconditions

  • Attack surface: Remotely accessible payment report functionality
  • Required access: Access to submit requests containing the period parameter; authentication requirements may vary by deployment
  • Trigger point: Processing of the period argument in pay_report.php
  • Why exploitation is possible: User-controlled input may influence SQL statement structure when it is not safely parameterized or validated

Why this happens

The underlying bug is improper neutralization of special elements in SQL commands, mapping to CWE-89: SQL Injection. The broader CWE-74 classification reflects the unsafe use of externally controlled input in an interpreted command language. The insecure pattern occurs when application input is concatenated into SQL statements or otherwise treated as query logic instead of being handled strictly as data.

Potential impact

  • An attacker may read sensitive records from the application database
  • Database contents may be modified or deleted
  • Account, payment, or reporting data could be corrupted
  • Application behavior may be disrupted
  • Database credentials or other stored secrets could be exposed

General mitigation guidance

Mitigation generally focuses on removing the ability for request data to alter SQL syntax.

Common defensive patterns include:

  • Use parameterized queries or prepared statements for all database operations
  • Apply allowlist validation to period values based on the expected format and permitted range
  • Avoid constructing SQL through string concatenation
  • Use database accounts with only the permissions required by the reporting function
  • Keep sensitive database operations behind appropriate authentication and authorization controls
  • Treat validation as a supplementary control rather than a replacement for query parameterization

How teams detect issues like this

Detection approaches may include:

  • Static analysis rules identifying SQL construction through string concatenation
  • Code review checks for direct use of request parameters in database queries
  • Dynamic testing of report parameters with unexpected characters and boundary values
  • Web application firewall or gateway policies that monitor suspicious query-manipulation patterns
  • Database monitoring for unusual queries, unexpected access patterns, or excessive error responses

Automated security review tools can help identify unsafe query-building patterns during development.

Sources

SourceLink
github.comgithub.com/zuojiu567/cve/issues/3
vuldb.comvuldb.com/cve/CVE-2026-90516
vuldb.comvuldb.com/submit/912055
vuldb.comvuldb.com/vuln/403102
vuldb.comvuldb.com/vuln/403102/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes, the affected report functionality is described as remotely reachable. Exploitability still depends on deployment exposure, authentication, authorization, and any network controls protecting the endpoint.

The attacker must be able to submit a request containing the affected period parameter. Whether an authenticated account is required depends on how the application is configured and deployed.

Use parameterized queries or prepared statements so the period value is always treated as data. Strict allowlist validation and least-privilege database permissions provide additional protection.

Standardize safe database-access APIs, review all request-to-query data flows, test parameters for injection behavior, and enforce secure coding checks in development and deployment pipelines.

Find out what's already
exploitable in your codebase.