/

CVE-2026-93972

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in SourceCodester Reviewer System

CVE-2026-93972

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 remotely reachable SQL injection vulnerability in SourceCodester Online Reviewer Management System 1.0 allows attacker-controlled input in the courseID argument to influence database queries.

If the affected endpoint is accessible and input is not safely handled, an attacker may be able to read, modify, or interfere with application data.

Affected context

The vulnerability occurs in the assessment-related functionality under /reviewer_0/admins/assessments/course/btn_functions.php. It may affect deployments where the endpoint is exposed to remote users and the courseID parameter reaches database query construction without sufficient parameterization or validation.

Exploit preconditions

  • Attack surface: Remotely accessible web application endpoint
  • Required access: Access sufficient to reach the affected assessment or course-management function; authentication requirements may depend on deployment configuration
  • Trigger point: Processing of the courseID argument
  • Why exploitation is possible: Attacker-controlled input may be incorporated into a SQL statement without being treated strictly as data

Why this happens

The underlying issue is an injection flaw in which externally supplied courseID data can influence SQL query structure. This maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection) and is also related to CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component. The insecure pattern is constructing or executing database queries with untrusted input instead of using parameterized statements and constrained input handling.

Potential impact

  • An attacker may read unauthorized records from the application database.
  • An attacker could alter or delete application data, depending on database permissions.
  • The vulnerability may enable unauthorized access to reviewer, course, assessment, or administrative information.
  • Database availability or application integrity could be affected.

General mitigation guidance

Mitigation generally centers on ensuring that all database operations treat request parameters as data rather than executable query syntax.

Common defensive patterns include:

  • Using parameterized queries or prepared statements for every database operation
  • Applying allowlist validation and type constraints to identifier fields such as courseID
  • Avoiding dynamic SQL construction from request parameters
  • Limiting the database account to the minimum required privileges
  • Separating administrative endpoints from broader network exposure where practical
  • Returning generic database errors and avoiding disclosure of query details

These controls reduce both direct injection risk and the potential impact of a compromised application account.

How teams detect issues like this

Detection approaches can include:

  • Static analysis for string concatenation or interpolation of request parameters into SQL statements
  • Code review of database calls in btn_functions.php and related administrative handlers
  • Dynamic application testing using benign input-variation checks against the affected parameter
  • Web application firewall or API policy rules for suspicious SQL metacharacter and operator patterns
  • Monitoring for unusual database errors, query volume, access patterns, or data retrieval from administrative endpoints

Automated security review tools may help identify unsafe query construction, but findings should be validated against the application's actual database access layer.

Sources

SourceLink
github.comgithub.com/orzl1/cve/issues/1
vuldb.comvuldb.com/cve/CVE-2026-93972
vuldb.comvuldb.com/submit/944506
vuldb.comvuldb.com/submit/944534
vuldb.comvuldb.com/vuln/407931
vuldb.comvuldb.com/vuln/407931/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes. The affected functionality is described as remotely reachable, although actual exploitability depends on endpoint exposure, authentication controls, and deployment configuration.

The attacker must be able to send requests to the affected function. Whether an authenticated account is required depends on how the application protects the administrative assessment features.

Use parameterized database queries together with strict type and allowlist validation for courseID and other request parameters.

Enforce secure database-access patterns through shared data-access libraries, code review, static analysis, least-privilege database accounts, and monitoring for abnormal query behavior.

Find out what's already
exploitable in your codebase.