CVE-2026-3751
SQL Injection in SourceCodester Employee Task Management System
Publication date: 2026-03-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 |
|---|---|---|
| oretnom23 | employee_task_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?
[{'type': 'paragraph', 'content': 'CVE-2026-3751 is a SQL injection vulnerability found in SourceCodester Employee Task Management System version 1.0. It exists in the GET parameter "date" of the file /daily-attendance-report.php. The vulnerability occurs because the application does not properly sanitize user input passed via this parameter, allowing an attacker to inject malicious SQL commands.'}, {'type': 'paragraph', 'content': 'This vulnerability is a time-based blind SQL injection, meaning the attacker can infer database information by observing response delays caused by injected SQL commands such as the MySQL SLEEP() function.'}, {'type': 'paragraph', 'content': 'Exploitation requires authentication, typically with default admin credentials, and can be performed remotely. The attacker can use this flaw to enumerate the database schema and retrieve sensitive data.'}] [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability impacts the confidentiality, integrity, and availability of the affected system.
- An attacker can perform unauthorized data exfiltration by extracting sensitive information such as employee records and admin credentials.
- The attacker can manipulate the database through injected SQL commands, potentially altering or damaging data.
- Because the attack can be performed remotely after authentication, it increases the risk of unauthorized access and data breaches.
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': 'The vulnerability can be detected by targeting the GET parameter "date" in the /daily-attendance-report.php file of the SourceCodester Employee Task Management System version 1.0. Since it is a time-based blind SQL injection, detection involves sending crafted requests that cause measurable delays in the server response.'}, {'type': 'paragraph', 'content': 'One practical method is to use sqlmap, a popular automated SQL injection tool, to test the "date" parameter for time-based blind SQL injection. An example payload used to confirm the vulnerability is: date=51201-02-02\') AND (SELECT 1850 FROM (SELECT(SLEEP(5)))lFrX) AND (\'KypN\'=\'KypN'}, {'type': 'paragraph', 'content': 'The command to run sqlmap would be similar to: sqlmap -u "http://target/daily-attendance-report.php?date=2026-01-01" --cookie="session=your_session_cookie" --technique=T --dbms=MySQL --level=5 --risk=3'}, {'type': 'paragraph', 'content': 'Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:daily-attendance-report.php'}] [1, 3]
What immediate steps should I take to mitigate this vulnerability?
No known mitigations or countermeasures have been documented for this vulnerability.
The suggested immediate step is to replace the affected product or component with a secure version or alternative.
Since the vulnerability requires authentication, restricting access to authorized users and changing default credentials (such as admin/admin) can reduce risk.
Implementing proper input sanitization and parameterized queries in the application code would be a long-term fix, but no patch or update is currently documented.