CVE-2026-2221
SQL Injection in code-projects Online Reviewer Login Component
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-2221 is a critical SQL injection vulnerability in the Online Reviewer System version 1.0, specifically in the /login/index.php file of the Login component. The vulnerability occurs because the "username" parameter is improperly handled and directly incorporated into SQL queries without proper sanitization or validation. This flaw allows remote attackers to inject malicious SQL code, enabling unauthorized database access and manipulation without requiring authentication.'}, {'type': 'paragraph', 'content': 'Attackers can exploit this vulnerability using various SQL injection techniques such as boolean-based blind, error-based, stacked queries, and time-based blind injections. Example payloads demonstrate how attackers can manipulate the username parameter to execute arbitrary SQL commands.'}, {'type': 'paragraph', 'content': 'Immediate remediation involves implementing prepared statements with parameter binding, enforcing strict input validation, and minimizing database user privileges.'}] [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, allowing attackers to read, modify, or delete sensitive data. It compromises the confidentiality, integrity, and availability of the system.
Exploitation can lead to full system compromise or service disruption, as attackers can execute arbitrary SQL commands remotely without authentication.
The vulnerability poses significant risks to system security and data integrity, making immediate corrective actions necessary to protect 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 testing the login endpoint (/login/index.php) for SQL injection flaws using crafted payloads targeting the username parameter.'}, {'type': 'paragraph', 'content': 'Common detection methods include using automated tools like sqlmap to send specially crafted POST requests to the login page.'}, {'type': 'list_item', 'content': 'Example sqlmap command: sqlmap -u "http://target/login/index.php" --data="username=test&password=test" --risk=3 --level=5 --batch'}, {'type': 'list_item', 'content': "Manual payloads to test include: \n- Boolean-based blind: username=test' OR NOT 8975=8975 #\n- Error-based: username=test' AND GTID_SUBSET(CONCAT(0x7170626a71,(SELECT (ELT(6345=6345,1))),0x71786a6271),6345)-- Zbva\n- Stacked queries: username=test';SELECT SLEEP(5) #\n- Time-based blind: username=test' AND (SELECT 3690 FROM (SELECT(SLEEP(5)))uKeS)-- ixeX"}] [1]
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 injection.
- Enforce strict input validation and filtering to ensure inputs conform to expected formats.
- Minimize database user privileges by avoiding the use of high-privilege accounts (e.g., root or admin) for routine database operations.
If possible, replace the affected software with an alternative product that does not contain this vulnerability.