CVE-2026-2089
SQL Injection in SourceCodester Online Class Record System Allows Remote Exploitation
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-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-2089 is a critical SQL injection vulnerability found in version 1.0 of the SourceCodester Online Class Record System, specifically in the file /admin/subject/controller.php.'}, {'type': 'paragraph', 'content': "The vulnerability arises because the 'id' parameter is improperly handled and directly incorporated into SQL queries without adequate input validation or sanitization."}, {'type': 'paragraph', 'content': 'This flaw allows attackers to inject malicious SQL code remotely without requiring authentication, enabling unauthorized manipulation of database queries.'}] [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to extract sensitive information, modify or delete data, and gain full control over the system.
It can also cause service disruptions and compromise the confidentiality, integrity, and availability of the affected system.
Since the attack can be performed remotely without authentication, the system is highly susceptible to exploitation.
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 vulnerable endpoint `/admin/subject/controller.php` with manipulated `id` parameters to observe abnormal behavior such as delayed responses.'}, {'type': 'paragraph', 'content': 'A proof-of-concept command uses a time-based blind SQL injection payload to confirm the vulnerability by causing a delay in the server response:'}, {'type': 'list_item', 'content': 'curl "http://127.0.0.1/ClassRecord/admin/subject/controller.php?action=delete&id=1 AND (SELECT 3191 FROM (SELECT(SLEEP(5)))ddEj)"'}, {'type': 'paragraph', 'content': 'Additionally, automated tools like sqlmap can be used to detect and enumerate the vulnerability by targeting the `id` parameter with crafted HTTP GET requests.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Use prepared statements with parameter binding to separate SQL code from user input, preventing injection.
- Implement strict input validation and filtering to ensure inputs conform to expected formats.
- Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts like root or admin for routine operations.
- Conduct regular security audits of code and systems to detect and address vulnerabilities promptly.