CVE-2026-2172
SQL Injection in code-projects Online Admission Login Endpoint
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_application_system_for_admission | 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?
CVE-2026-2172 is a SQL Injection vulnerability in the Online Application System for Admission 1.0 by code-projects, specifically in the Login Endpoint located in enrollment/index.php.
The vulnerability occurs because the application constructs SQL queries by directly concatenating user input without proper sanitization or use of parameterized queries.
This flaw allows attackers to inject malicious SQL code into input fields, such as login forms, which can manipulate the SQL logic to bypass authentication or perform unauthorized database operations.
A proof-of-concept involves sending a specially crafted POST request that causes the SQL WHERE clause to always evaluate as true, enabling attackers to bypass login controls, including administrative access.
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 for SQL injection flaws. A proof-of-concept involves sending a POST request to the login endpoint with a payload such as `u_id=admin' OR '1'='1` and any password, which causes the SQL WHERE clause to always evaluate to true, potentially bypassing authentication."}, {'type': 'paragraph', 'content': 'Additionally, attackers can identify vulnerable targets using Google dorking with queries like `inurl:enrollment/index.php`.'}, {'type': 'paragraph', 'content': 'To detect the vulnerability on your system, you can use tools like curl or sqlmap to test the login form. For example, a curl command to test the login endpoint might be:'}, {'type': 'list_item', 'content': 'curl -X POST -d "u_id=admin\' OR \'1\'=\'1&password=any" http://target/enrollment/index.php'}, {'type': 'paragraph', 'content': 'If the response indicates successful authentication or unusual behavior, the system is likely vulnerable.'}] [1, 2]
What immediate steps should I take to mitigate this vulnerability?
No known mitigations or countermeasures have been reported for this vulnerability.
It is suggested to replace the affected component with an alternative product to avoid exploitation.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including authentication bypass, allowing attackers to gain unauthorized access to the system.
Attackers can exfiltrate sensitive data, modify or delete database records, and escalate privileges within the system.
It may also enable lateral movement or further exploitation depending on the database privileges compromised.
The attack can be launched remotely without any authentication, making it easier for attackers to exploit.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know