CVE-2026-93972

7.3

SourceCodester · Online Reviewer Management System

A SQL injection vulnerability exists in SourceCodester Online Reviewer Management System 1.0 within the courseID parameter of btn_functions.php, allowing unauthenticated remote code execution.

Executive summary

A critical SQL injection vulnerability in SourceCodester Online Reviewer Management System 1.0 allows unauthenticated remote attackers to compromise the underlying database.

Vulnerability

The application fails to properly sanitize the courseID parameter in the /reviewer_0/admins/assessments/course/btn_functions.php file before using it in SQL queries. This flaw allows an unauthenticated attacker to inject malicious SQL commands to manipulate database operations.

Business impact

Successful exploitation of this vulnerability can lead to unauthorized access to sensitive information, data tampering, or complete compromise of the backend database. Given the CVSS score of 7.3, this represents a high risk to business continuity and data integrity, potentially exposing administrative credentials or reviewer records to malicious actors.

Remediation

Immediate Action: As no official vendor patch is currently available, administrators should restrict network access to the affected script or disable the impacted module entirely.

Proactive Monitoring: Review web server access logs for anomalous GET requests targeting btn_functions.php, specifically looking for SQL syntax patterns such as SLEEP, RLIKE, or UNION SELECT statements.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection payloads targeting URL parameters.

Exploitation status

Public Exploit Available: Yes, a published proof-of-concept exists as documented in the GitHub issue referenced in the vulnerability research write-up.

Analyst recommendation

Due to the lack of an official patch and the availability of public exploit material, this vulnerability poses a significant risk to any organization deploying this software. We strongly recommend isolating the affected application from public-facing networks until the vendor provides a secure update or implementing strict input validation as a temporary code-level fix.

More SourceCodester CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by pnpe (VulDB User), per the CVE Program record.