CVE-2026-2223
SQL Injection in code-projects Online Reviewer System 1.0 Allows Remote Exploitation
Publication date: 2026-02-09
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| fabian | 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. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-2223 is a critical SQL injection vulnerability in the Online Reviewer System 1.0, specifically in the file /system/system/students/assessments/pretest/take/index.php. The vulnerability occurs because the "id" parameter is not properly sanitized or validated before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without any authentication.'}, {'type': 'paragraph', 'content': 'The vulnerability can be exploited using various SQL injection techniques such as Boolean-based blind SQL injection, error-based SQL injection, stacked queries, and time-based blind SQL injection. These methods enable attackers to manipulate the database queries executed by the system.'}] [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to read sensitive information, modify or delete data, and potentially compromise the entire system.
Because no authentication is required to exploit this flaw, attackers can remotely execute malicious SQL commands, which may result in data leakage, data manipulation, full system compromise, and disruption of services.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "The vulnerability can be detected by testing the 'id' parameter in the URL path /system/system/students/assessments/pretest/take/index.php for SQL injection flaws."}, {'type': 'paragraph', 'content': "Example detection methods include using SQL injection payloads such as Boolean-based blind SQL injection with MySQL RLIKE operator, error-based SQL injection exploiting MySQL GTID_SUBSET function, stacked queries like SELECT SLEEP(5), and time-based blind SQL injection using MySQL's SLEEP function."}, {'type': 'paragraph', 'content': 'A practical approach is to use automated tools like sqlmap to confirm the injection point and identify the database backend.'}, {'type': 'list_item', 'content': 'Use sqlmap with a command like: sqlmap -u "http://target/system/system/students/assessments/pretest/take/index.php?id=1" --batch --dbs'}, {'type': 'list_item', 'content': "Manually test injection by appending payloads such as '1' OR '1'='1'-- or '1' AND SLEEP(5)-- to the id parameter and observe response delays or errors."}, {'type': 'list_item', 'content': 'Use Google dorking to identify vulnerable targets with the query: inurl:system/system/students/assessments/pretest/take/index.php'}] [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input.
Enforce strict input validation and filtering to ensure that inputs conform to expected formats and do not contain malicious SQL code.
Minimize database user privileges by avoiding the use of high-privilege accounts for routine database operations.
If possible, replace the affected component with an alternative product that is not vulnerable.
Taking these corrective actions promptly is essential to protect system security and maintain data integrity.