CVE-2026-2912
SQL Injection in Online Reviewer System's Student Result Module
Publication date: 2026-02-22
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
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data.
It can result in data leakage, data manipulation, full system compromise, and potential service disruption.
Since the attack can be launched remotely without authentication, it is highly accessible and dangerous.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
Can you explain this vulnerability to me?
CVE-2026-2912 is a critical SQL injection vulnerability in version 1.0 of the code-projects Online Reviewer System. It exists in the file /system/system/students/assessments/results/studentresult-view.php due to improper handling of the test_id parameter.
The vulnerability arises because the test_id argument is used in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code.
This flaw enables remote attackers to manipulate SQL commands without authentication, potentially compromising the confidentiality, integrity, and availability of the system.
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 handling of the `test_id` parameter in the URL path `/system/system/students/assessments/results/studentresult-view.php` for SQL injection flaws.'}, {'type': 'paragraph', 'content': 'One method to identify vulnerable targets is using Google dorking with the query: `inurl:system/system/students/assessments/results/studentresult-view.php`.'}, {'type': 'paragraph', 'content': 'For active testing, tools like sqlmap can be used to automate detection and exploitation attempts against the `test_id` parameter.'}, {'type': 'list_item', 'content': 'Example sqlmap command: `sqlmap -u "http://target/system/system/students/assessments/results/studentresult-view.php?test_id=1" --batch --dbs`'}, {'type': 'list_item', 'content': "Manual testing can include injecting typical SQL payloads into the `test_id` parameter, such as `' OR '1'='1` or time-based payloads like `1' AND SLEEP(5)-- ` to observe delays or errors."}] [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to ensure that user input is not directly incorporated into SQL queries.
Strict input validation and filtering should be enforced on the `test_id` parameter to allow only expected formats and reject malicious input.
Database user permissions should be restricted to the minimum necessary privileges, avoiding the use of high-privilege accounts for routine operations.
If possible, replace the affected component or upgrade to a version without this vulnerability, as no known patches or countermeasures have been documented.