CVE-2026-36919
SQL Injection in Sourcecodester Online Reviewer System Admin Module
Publication date: 2026-04-13
Last updated on: 2026-04-14
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| janobe | online_reviewer_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-36919 is an SQL Injection vulnerability in the Online Reviewer System v1.0 by Sourcecodester. It specifically affects the file `/reviewer/system/system/admins/assessments/examproper/exam-update.php`.
The vulnerability occurs because the `test_id` GET parameter in the URL is not properly sanitized before being used in SQL queries. This allows an attacker to inject arbitrary SQL commands.
For example, an attacker can use a UNION-based SQL injection payload to retrieve sensitive information such as the current database name.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized data leakage from the backend database.
An attacker exploiting this SQL injection could retrieve sensitive information stored in the database.
Additionally, it may allow further database manipulation, potentially compromising the integrity and confidentiality of the system's data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the `test_id` GET parameter in the URL `/reviewer/system/system/admins/assessments/examproper/exam-update.php` for SQL injection.
A common detection method is to inject a payload that attempts to exploit the SQL injection, such as: `-test_id=-93' union select 1,2,3,4,5,6,database(),8,9,10--+`.
You can use tools like curl or a web proxy to send HTTP requests with this payload and observe if the database name or other unexpected data is returned, indicating vulnerability.
- Example curl command to test the injection: curl "http://[target]/reviewer/system/system/admins/assessments/examproper/exam-update.php?test_id=-93'%20union%20select%201,2,3,4,5,6,database(),8,9,10--+" -H "Cookie: PHPSESSID=[session_id]"
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability is an SQL injection that allows unauthorized data leakage and potentially further database manipulation. Such unauthorized access to sensitive data can lead to non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and breaches.
By enabling attackers to extract or manipulate database contents, this vulnerability could result in exposure of personal or protected health information, thereby violating confidentiality and integrity requirements mandated by these standards.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the SQL Injection vulnerability in the Online Reviewer System v1.0, immediate steps include sanitizing and validating the 'test_id' parameter to prevent injection of malicious SQL code.
Implement prepared statements or parameterized queries in the code handling the 'test_id' parameter to ensure that user input is not directly embedded into SQL queries.
Restrict database permissions to limit the impact of any potential injection and monitor logs for suspicious activity related to the vulnerable endpoint.
If possible, apply any available patches or updates from the vendor or source code repository that address this vulnerability.