CVE-2026-2171
SQL Injection in code-projects Online Student Management System Login
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_student_management_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-2171 is a critical SQL injection vulnerability found in version 1.0 of the code-projects Online Student Management System, specifically in the accounts.php file within the Login component.
The vulnerability arises from improper handling of the username and password input parameters, which are used to construct SQL commands without adequate sanitization or neutralization of special characters.
This flaw allows remote attackers to execute arbitrary SQL commands without requiring authentication by manipulating the username or password arguments.
The vulnerability corresponds to CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) and is easy to exploit, with a public proof-of-concept exploit available.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to authentication bypass, allowing attackers to log in without valid credentials.
Attackers can enumerate and exfiltrate sensitive database records, including user and system data.
They may modify or delete data, potentially causing data loss or corruption.
Depending on the privileges of the compromised account, attackers could gain full database access, impacting 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 testing for SQL injection points in the login functionality, specifically targeting the username and password parameters in accounts.php.'}, {'type': 'paragraph', 'content': "One common method is to attempt SQL injection payloads such as using a username like ' OR '1'='1 with any password to see if authentication can be bypassed."}, {'type': 'paragraph', 'content': 'Additionally, searching for the vulnerable endpoint using Google Dorking with queries like inurl:accounts.php can help identify exposed targets.'}, {'type': 'paragraph', 'content': 'Example commands to test the vulnerability include sending HTTP requests with crafted parameters, for instance using curl:'}, {'type': 'list_item', 'content': 'curl -X POST -d "username=\' OR \'1\'=\'1&password=anything" http://targetsite.com/accounts.php'}, {'type': 'list_item', 'content': 'curl -X POST -d "username=admin&password=\' OR \'1\'=\'1" http://targetsite.com/accounts.php'}, {'type': 'paragraph', 'content': 'Observing successful authentication bypass or unusual responses indicates the presence of the vulnerability.'}] [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product, as no known mitigations or countermeasures have been documented.
If replacement is not immediately possible, restricting access to the vulnerable accounts.php endpoint through network controls or web application firewalls may reduce exposure.
Implementing input validation and using prepared statements or parameterized queries in the source code can prevent SQL injection, but this requires code changes.
Monitoring logs for suspicious login attempts and unusual database activity can help detect exploitation attempts.