/

CVE-2026-90877

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Faculty Clearance System

CVE-2026-90877

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database compromise and unauthorized 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

A high-severity SQL injection vulnerability in the Online Faculty Clearance System allows remotely supplied input to influence database queries through the haydi parameter of update_requirement_status.php.

If the affected endpoint is reachable and does not safely separate data from SQL commands, an attacker may read, alter, or interfere with application data. Public exploit availability increases the likelihood of active probing.

Affected context

The vulnerability occurs in deployments of SourceCodester Online Faculty Clearance System 1.0 where the update_requirement_status.php endpoint is accessible over the network and processes the haydi argument in a database operation. Risk depends on how the application constructs queries, the privileges of its database account, and whether additional access controls or filtering are present.

Exploit preconditions

  • Attack surface: Network-accessible web endpoint
  • Required access: The ability to send requests to update_requirement_status.php; authentication requirements depend on deployment configuration
  • Trigger point: Processing of the haydi parameter
  • Why exploitation is possible: Input may be incorporated into a SQL statement without reliable parameter separation or equivalent query safeguards

Why this happens

The underlying bug is an unsafe boundary between externally controlled input and database query construction. When application data is concatenated into SQL commands, specially structured input may change the intended meaning of the query instead of remaining a literal value. This 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 classification for improper neutralization in an interpreted command context.

Potential impact

  • An attacker may retrieve sensitive database records
  • An attacker could modify or delete application data
  • Database-backed authorization or workflow information may be altered
  • The application may experience service disruption
  • Compromised database credentials or excessive database privileges could increase downstream impact

General mitigation guidance

Mitigation generally centers on keeping untrusted input separate from executable SQL syntax.

Common defensive patterns include:

  • Use parameterized queries or prepared statements for all database operations
  • Apply allowlist-based validation appropriate to the expected data type and business rules
  • Avoid constructing SQL statements through string concatenation
  • Use database accounts with only the permissions required by the application
  • Return generic database errors to users while recording useful details in protected logs
  • Enforce authentication and authorization at sensitive endpoint boundaries
  • Treat client-side validation as supplementary rather than a trust boundary

How teams detect issues like this

Organizations can look for SQL injection exposure through:

  • Static analysis rules identifying string concatenation or interpolation in database queries
  • Code review checks for unparameterized query APIs and unsafe query-building helpers
  • Dynamic application testing using non-destructive input variations and monitored test environments
  • Web application firewall or gateway policies that detect anomalous database-oriented request patterns
  • Database audit logs showing unexpected query structure, access patterns, or privilege use
  • Automated security review tools that flag data flowing from request parameters into SQL execution functions

Sources

SourceLink
github.comgithub.com/OnlyCMJB/cve/issues/3
vuldb.comvuldb.com/cve/CVE-2026-90877
vuldb.comvuldb.com/submit/927383
vuldb.comvuldb.com/vuln/403471
vuldb.comvuldb.com/vuln/403471/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes, the affected web endpoint is described as remotely reachable. Practical exploitability still depends on network exposure, authentication, authorization, and runtime configuration.

Not necessarily. The required access depends on the application's endpoint controls and whether an attacker can reach the request handler without valid credentials.

Use parameterized queries or prepared statements, validate input according to its expected type, and avoid incorporating request values directly into SQL syntax.

Combine secure database APIs with code review, static analysis, endpoint authorization, least-privilege database accounts, and controlled dynamic security testing.

Find out what's already
exploitable in your codebase.