CVE-2026-5182
Remote SQL Injection in SourceCodester Teacher Record System Parameter Handler
Publication date: 2026-03-31
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 |
|---|---|---|
| sourcecodester | teacher_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?
This vulnerability is a SQL injection flaw found in the Teacher Record System version 1.0, specifically in the file `/trms/search-teacher.php`. It occurs because the `searchteacher` parameter is improperly handled and directly included in SQL queries without proper input validation or sanitization.
An attacker can exploit this by injecting malicious SQL code through the `searchteacher` parameter, which allows unauthorized manipulation of the database.
The attack can be performed remotely without any authentication, making it easier for attackers to exploit.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to leak sensitive data, modify or delete records, and gain full control over the system.
It can also cause service disruptions, impacting the availability and integrity of the Teacher Record System.
Since no authentication is required, the risk of exploitation is higher, potentially affecting all users and data managed by the system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the `searchteacher` parameter in the `/trms/search-teacher.php` file for injection flaws.
A practical approach is to use automated tools like sqlmap to test the endpoint with the vulnerable parameter.
- Use sqlmap with a POST request targeting `/Teachers/trms/search-teacher.php` and the `searchteacher` parameter to identify time-based blind and boolean-based blind SQL injection.
- Example command: sqlmap -u "http://target/Teachers/trms/search-teacher.php" --data="searchteacher=test" --risk=3 --level=5
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Implement prepared statements with parameter binding to separate SQL code from user input.
- Apply 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.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Teacher Record System allows attackers to perform unauthorized database access, leak sensitive data, modify or delete records, and gain control over the system without authentication.
Such unauthorized access and potential data leakage can lead to non-compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data against unauthorized access and breaches.
Failure to protect sensitive data due to this vulnerability could result in violations of data privacy and security requirements mandated by these regulations.