CVE-2026-37597
SQL Injection in SourceCodester WFH Attendance System
Publication date: 2026-04-14
Last updated on: 2026-04-14
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sourcecodester | online_employees_work_from_home_attendance_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. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Online Employees Work From Home Attendance System v1.0 allows unauthorized access to sensitive information by exploiting improper input validation in the admin attendance list feature.
Such unauthorized data access can lead to exposure of personal or sensitive employee data, which may violate data protection regulations like GDPR or HIPAA that require safeguarding personal information against unauthorized access.
Therefore, this vulnerability could negatively impact compliance with these common standards and regulations by enabling data breaches or unauthorized data disclosure.
Can you explain this vulnerability to me?
CVE-2026-37597 is an SQL injection vulnerability found in the Online Employees Work From Home Attendance System v1.0 by Sourcecodester. The vulnerability exists in the file /wfh_attendance/admin/attendance_list.php, specifically in the date_end parameter of the URL query string.
An attacker can exploit this vulnerability by injecting malicious SQL code into the date_end parameter, which is not properly sanitized or validated. This allows the attacker to manipulate the SQL query executed by the application.
For example, an attacker can use a UNION-based SQL injection payload to retrieve sensitive information such as the SQLite database version, demonstrating the ability to execute arbitrary SQL commands and extract data.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to gain unauthorized access to sensitive data stored in the database by manipulating SQL queries.
Exploitation of this vulnerability could lead to data leakage, unauthorized data modification, or further compromise of the system.
Since the vulnerability is in the admin panel's attendance list feature, it could expose sensitive employee attendance records or other confidential information.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the SQL injection point in the `date_end` parameter of the URL query string in the admin attendance list page.
A typical detection method involves sending a crafted GET request to the vulnerable URL with a malicious payload in the `date_end` parameter to check for SQL injection.
- Example of a test payload to detect the vulnerability: `2026-03-12' union select 1,2,3,4,5,6,7,8,sqlite_version(),10,11,12--+`
- Example curl command to test the vulnerability: `curl "http://<target>/wfh_attendance/admin/?page=attendance_list&employee_id=1&date_start=2026-03-05&date_end=2026-03-12'%20union%20select%201,2,3,4,5,6,7,8,sqlite_version(),10,11,12--+"`
If the response contains database version information or unusual data, it indicates the presence of the SQL injection vulnerability.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating all user inputs, especially the `date_end` parameter in the attendance list feature.
Implement prepared statements or parameterized queries to prevent SQL injection attacks.
Restrict access to the vulnerable admin page to trusted users only and monitor logs for suspicious activity.
If possible, apply patches or updates from the vendor or disable the vulnerable functionality until a fix is available.