CVE-2026-2199
SQL Injection in 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-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-2199 is a critical SQL injection vulnerability found in code-projects Online Reviewer System version 1.0, specifically in the file /reviewer/system/system/admins/manage/users/user-delete.php.'}, {'type': 'paragraph', 'content': "The vulnerability arises from improper handling of the 'ID' parameter, which is manipulated to inject malicious SQL code due to inadequate neutralization of special characters in the input."}, {'type': 'paragraph', 'content': 'This flaw allows remote attackers to execute SQL injection attacks without requiring any authentication.'}, {'type': 'paragraph', 'content': 'Attackers can exploit this vulnerability by sending specially crafted inputs to the vulnerable parameter, enabling them to execute arbitrary SQL commands on the database.'}] [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to retrieve, modify, or delete sensitive data.
Attackers can perform data leakage, data tampering, full system control, and service disruption.
Since no authentication is required, the attack can be initiated remotely by anyone aware of the vulnerability.
The vulnerability impacts the confidentiality, integrity, and availability of the system.
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 identifying attempts to exploit the SQL injection flaw in the 'id' parameter of the vulnerable URL path `/reviewer/system/system/admins/manage/users/user-delete.php`."}, {'type': 'paragraph', 'content': 'Attackers may use SQL injection payloads such as Boolean-based blind SQL injection, error-based SQL injection, stacked queries, and time-based blind SQL injection targeting this parameter.'}, {'type': 'paragraph', 'content': 'One detection method is to monitor web server logs or network traffic for suspicious requests containing SQL injection payloads or unusual query parameters targeting the vulnerable URL.'}, {'type': 'list_item', 'content': 'Use Google dorking with the query `inurl:reviewer/system/system/admins/manage/users/user-delete.php` to identify exposed instances.'}, {'type': 'list_item', 'content': 'Use sqlmap or similar automated SQL injection detection tools with payloads targeting the \'id\' parameter, for example: `sqlmap -u "http://target/reviewer/system/system/admins/manage/users/user-delete.php?id=48" --risk=3 --level=5`.'}, {'type': 'list_item', 'content': "Manually test with payloads such as: `id=48' RLIKE (SELECT (CASE WHEN (4338=4338) THEN 48 ELSE 0x28 END))--` or `id=48';SELECT SLEEP(5) #` to observe abnormal responses or delays indicating SQL injection."}] [1, 2]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': "Immediate mitigation steps include preventing exploitation of the SQL injection vulnerability by addressing the root cause: unsanitized use of the 'id' parameter in SQL queries."}, {'type': 'list_item', 'content': 'Implement prepared statements with parameter binding to separate SQL code from user input.'}, {'type': 'list_item', 'content': "Apply strict input validation and filtering to ensure the 'id' parameter only accepts expected formats (e.g., numeric values)."}, {'type': 'list_item', 'content': "Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine operations."}, {'type': 'list_item', 'content': 'Conduct regular security audits and code reviews to detect and remediate vulnerabilities promptly.'}, {'type': 'paragraph', 'content': 'If immediate code fixes are not possible, consider replacing the affected component with an alternative product to avoid exploitation.'}] [1, 2, 3]