CVE-2026-2196
Analyzed Analyzed - Analysis Complete
SQL Injection in Online Reviewer System exam-update.php Allows Remote Exploit

Publication date: 2026-02-09

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was found in code-projects Online Reviewer System 1.0. This issue affects some unknown processing of the file /system/system/admins/assessments/pretest/exam-update.php. The manipulation of the argument test_id results in sql injection. The attack may be performed from remote. The exploit has been made public and could be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-09
Last Modified
2026-04-29
Generated
2026-06-16
AI Q&A
2026-02-09
EPSS Evaluated
2026-06-14
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
fabian online_reviewer_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-2196 is a critical SQL injection vulnerability in the Online Reviewer System version 1.0, specifically in the file /system/system/admins/assessments/pretest/exam-update.php.

The vulnerability arises from improper handling and inadequate validation of the test_id parameter, which is directly embedded into SQL queries without proper sanitization.

This flaw allows remote attackers to inject malicious SQL code without authentication, enabling them to manipulate SQL queries and perform unauthorized database operations.

Various SQL injection techniques can be used, including Boolean-based blind, error-based, stacked queries, time-based blind, and UNION-based SQL injection.

Impact Analysis

Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to read, modify, or delete sensitive data.

Potential impacts include data leakage, data tampering, full system compromise, and disruption of services, which pose severe risks to system security and business continuity.

Since the attack requires no authentication and can be performed remotely, it increases the risk of widespread exploitation.

Compliance Impact

I don't know

Detection Guidance

[{'type': 'paragraph', 'content': 'The vulnerability can be detected by testing the vulnerable parameter "test_id" in the URL /system/system/admins/assessments/pretest/exam-update.php for SQL injection flaws.'}, {'type': 'paragraph', 'content': 'One practical method is to use automated tools such as sqlmap to test and confirm the SQL injection vulnerability by injecting payloads and attempting data extraction.'}, {'type': 'paragraph', 'content': 'An example of a manual test payload is to append a UNION-based SQL injection string to the test_id parameter, such as:'}, {'type': 'list_item', 'content': "http://localhost:83/system/system/admins/assessments/pretest/exam-update.php?test_id=151' UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,NULL,CONCAT(0x716b626a71,0x6641574a457465437858724c446c4a73554c566755634e75616d6473754c66587470647476567350,0x7171626a71),NULL,NULL #"}, {'type': 'paragraph', 'content': 'Additionally, Google dorking can be used to identify vulnerable targets by searching for URLs containing the vulnerable path, for example:'}, {'type': 'list_item', 'content': 'inurl:system/system/admins/assessments/pretest/exam-update.php'}] [1, 2]

Mitigation Strategies

Immediate mitigation steps include implementing prepared statements with parameter binding to ensure that user input is properly separated from SQL commands, preventing injection.

Strict input validation and filtering should be enforced to ensure that inputs conform to expected formats and do not contain malicious content.

Database user permissions should be restricted to the minimum necessary privileges, avoiding the use of high-privilege accounts for routine operations.

Since no official patches or fixes are available, consider replacing the affected component with an alternative product if possible.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-2196. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart