CVE-2026-2220
SQL Injection in code-projects Online Reviewer System 1.0 Allows Remote Exploit
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
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Implement prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection.
- Apply strict input validation and filtering on the difficulty_id parameter to ensure it conforms to expected formats and reject malicious input.
- Minimize database user privileges by avoiding the use of high-privilege accounts for routine database operations.
- If possible, replace or update the affected component to a version or alternative product that is not vulnerable.
These steps help protect the system from unauthorized database access, data leakage, and potential full system compromise.
Can you explain this vulnerability to me?
CVE-2026-2220 is a critical SQL injection vulnerability in the Online Reviewer System version 1.0, specifically in the file /system/system/admins/assessments/pretest/btn_functions.php. The vulnerability occurs because the difficulty_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 authentication.
The flaw enables attackers to manipulate SQL queries, potentially leading to unauthorized database access, data leakage, data tampering, and full system compromise. Various SQL injection techniques such as Boolean-based blind, error-based, and time-based blind SQL injection can be used to exploit this vulnerability.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, modification or deletion of data, and disruption of system availability. Attackers can exploit the flaw to compromise the confidentiality, integrity, and availability of the affected system.
- Unauthorized database access
- Data leakage and exposure of sensitive information
- Data tampering or deletion
- Full system compromise
- Potential service disruption
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 monitoring for exploitation attempts targeting the "difficulty_id" parameter in POST requests to the file /system/system/admins/assessments/pretest/btn_functions.php. Detection can involve looking for unusual or malicious SQL payloads in this parameter.'}, {'type': 'paragraph', 'content': 'Additionally, vulnerable targets can be identified using Google hacking queries such as: inurl:system/system/admins/assessments/pretest/btn_functions.php'}, {'type': 'paragraph', 'content': 'For active detection on your system, you can use web server logs or network monitoring tools to filter POST requests containing the "difficulty_id" parameter with suspicious SQL injection patterns.'}, {'type': 'paragraph', 'content': 'Example commands to detect suspicious POST requests might include:'}, {'type': 'list_item', 'content': "Using grep on web server logs to find POST requests with difficulty_id: grep -i 'difficulty_id=' /var/log/apache2/access.log"}, {'type': 'list_item', 'content': 'Using network packet capture tools like tcpdump or Wireshark to filter HTTP POST traffic to the vulnerable endpoint and inspect the difficulty_id parameter.'}, {'type': 'list_item', 'content': 'Using intrusion detection systems (IDS) with SQL injection detection rules targeting the difficulty_id parameter.'}] [3, 1]