CVE-2026-2166
SQL Injection in code-projects Online Reviewer Login Component
Publication date: 2026-02-08
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?
CVE-2026-2166 is a critical SQL injection vulnerability found in the Online Reviewer System version 1.0, specifically in the /login/index.php file within the Login component.
The vulnerability arises because the application improperly handles the username and password input parameters, incorporating them directly into SQL queries without proper sanitization or validation.
This flaw allows attackers to inject malicious SQL code remotely without any authentication, potentially modifying the intended SQL commands.
Exploitation can bypass authentication controls and manipulate the database, leading to unauthorized access and control over the system.
How can this vulnerability impact me? :
Exploiting this vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, modification or deletion of data, and disruption of service availability.
Attackers can bypass authentication, gain full system control, and tamper with data integrity and confidentiality.
The vulnerability affects 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 SQL injection vulnerability can be detected by testing the login interface, specifically the /login/index.php endpoint, for improper handling of the username and password parameters.'}, {'type': 'paragraph', 'content': "One approach is to attempt to inject SQL code into the username or password fields, such as using the input: admin' OR '1'='1, which can bypass authentication if the system is vulnerable."}, {'type': 'paragraph', 'content': 'Automated tools like sqlmap can be used to confirm the presence of the vulnerability by targeting the login endpoint with crafted payloads.'}, {'type': 'list_item', 'content': 'Use sqlmap to test the login page: sqlmap -u "http://target/login/index.php" --data="username=admin&password=admin" --risk=3 --level=5'}, {'type': 'list_item', 'content': "Manually test by sending POST requests with payloads such as username=admin' OR '1'='1 and password=admin' OR '1'='1 to see if authentication is bypassed."}, {'type': 'list_item', 'content': 'Use Google dorking to identify vulnerable targets by searching: inurl:login/index.php'}] [1, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves preventing the SQL injection by properly handling user inputs in the login functionality.
The recommended fix is to implement prepared statements with parameter binding, which separates SQL code from user input and prevents malicious input from being executed as SQL commands.
If fixing the code is not immediately possible, replacing the affected component with an alternative product is suggested.
Until a fix or replacement is applied, restrict access to the vulnerable login page and monitor for suspicious activity to reduce risk.