CVE-2026-2197
SQL Injection in Online Reviewer System exam-delete.php 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-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. |
| 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?
[{'type': 'paragraph', 'content': 'CVE-2026-2197 is a critical SQL injection vulnerability found in version 1.0 of the Online Reviewer System, specifically in the file /system/system/admins/assessments/pretest/exam-delete.php.'}, {'type': 'paragraph', 'content': 'The vulnerability arises because the "test_id" parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code.'}, {'type': 'paragraph', 'content': 'This flaw enables attackers to manipulate SQL queries remotely without authentication, potentially modifying, deleting, or extracting sensitive data from the database.'}] [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to view, modify, or delete sensitive information.
It can result in data leakage, data tampering, full system compromise, and disruption of services, posing severe risks to system security and business continuity.
- Unauthorized access to sensitive data
- Data modification or deletion
- Potential full system compromise
- 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': 'This vulnerability can be detected by testing the vulnerable parameter "test_id" in the URL path "/system/system/admins/assessments/pretest/exam-delete.php" for SQL injection flaws.'}, {'type': 'paragraph', 'content': 'One approach is to use SQL injection testing tools such as sqlmap to automate detection and exploitation attempts.'}, {'type': 'paragraph', 'content': "An example of a manual test is to append a crafted payload to the URL, such as: http://localhost:83/system/system/admins/assessments/pretest/exam-delete.php?test_id=151' AND 6812=(SELECT COUNT(*) FROM INFORMATION_SCHEMA.COLUMNS A, INFORMATION_SCHEMA.COLUMNS B, INFORMATION_SCHEMA.COLUMNS C WHERE 0 XOR 1)--"}, {'type': 'paragraph', 'content': 'This payload attempts a boolean-based blind SQL injection to verify if the parameter is vulnerable.'}, {'type': 'paragraph', 'content': 'Commands to detect the vulnerability include running sqlmap against the target URL with the vulnerable parameter, for example:'}, {'type': 'list_item', 'content': 'sqlmap -u "http://target/system/system/admins/assessments/pretest/exam-delete.php?test_id=1" --batch --dbs'}, {'type': 'list_item', 'content': 'curl "http://target/system/system/admins/assessments/pretest/exam-delete.php?test_id=1\' OR \'1\'=\'1"'}, {'type': 'paragraph', 'content': 'Additionally, Google dorking can be used to locate potentially vulnerable targets using the query: inurl:system/system/admins/assessments/pretest/exam-delete.php'}] [2, 3, 1]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps include implementing secure coding practices to prevent SQL injection.'}, {'type': 'list_item', 'content': 'Use prepared statements with parameterized queries to separate SQL code from user input.'}, {'type': 'list_item', 'content': 'Enforce strict input validation and filtering to ensure that the "test_id" parameter only accepts expected formats (e.g., numeric values).'}, {'type': 'list_item', 'content': 'Restrict database user permissions to the minimum necessary, avoiding the use of high-privilege accounts for routine operations.'}, {'type': 'paragraph', 'content': 'If possible, replace or update the affected component to a version that is not vulnerable.'}, {'type': 'paragraph', 'content': 'Until a fix is applied, consider implementing web application firewall (WAF) rules to detect and block SQL injection attempts targeting the vulnerable parameter.'}] [2, 3, 1]