CVE-2026-2087
SQL Injection in SourceCodester Online Class Record System Login
Publication date: 2026-02-07
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 |
|---|---|---|
| janobe | online_class_record_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-2087 is a critical SQL injection vulnerability found in version 1.0 of the SourceCodester Online Class Record System. The flaw exists in the /admin/login.php file due to improper validation and sanitization of the user_email parameter. This allows attackers to inject malicious SQL code into database queries.
Because of this vulnerability, attackers can manipulate the database queries to gain unauthorized access, retrieve, modify, or delete sensitive data. The attack can be performed remotely without any authentication, making it easy to exploit.
How can this vulnerability impact me? :
Exploitation of this SQL injection vulnerability can lead to unauthorized access to the database, resulting in data leakage, data tampering, and potential deletion of sensitive information.
Attackers may gain full control over the system, disrupt services, and compromise the confidentiality, integrity, and availability of the affected system.
Since the attack requires no authentication and can be initiated remotely, it poses a significant risk to business continuity and system security.
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 /admin/login.php endpoint for injection points in the user_email parameter.'}, {'type': 'paragraph', 'content': "A proof-of-concept payload to confirm the vulnerability is a time-based blind SQL injection such as: user_email=admin' AND (SELECT 1517 FROM (SELECT(SLEEP(5)))Hvvx) AND 'nnts'='nnts"}, {'type': 'paragraph', 'content': 'Using tools like sqlmap to send crafted POST requests to /ClassRecord/admin/login.php with parameters user_email, user_pass, and btnLogin can automate detection.'}, {'type': 'list_item', 'content': 'Example sqlmap command: sqlmap -u "http://target/ClassRecord/admin/login.php" --data="user_email=admin&user_pass=pass&btnLogin=Login" --time-sec=5 --technique=T --batch'}, {'type': 'list_item', 'content': 'Manual testing can be done by injecting SQL payloads into the user_email field and observing delayed responses or error messages.'}, {'type': 'list_item', 'content': 'Google dorking can help identify vulnerable targets using queries like: inurl:admin/login.php'}] [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate remediation steps include:
- Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection.
- Apply strict input validation and filtering to ensure inputs conform to expected formats.
- Minimize database user permissions by avoiding use of high-privilege accounts for routine operations.
- Conduct regular security audits to detect and fix vulnerabilities promptly.
- Consider replacing the affected software with an alternative product if immediate patching is not feasible.