A flaw has been found in IceHRM up to 35.0.1. This impacts an unknown function of the file core/src/Reports/User/Reports/EmployeeAttendanceReport.php of the component UserReport Endpoint. Executing a manipulation of the argument employeeList can lead to sql injection. The attack can be launched remotely. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.
Security readout for executives and security teams
Plain-English summary
CVE-2026-15478 is a reported SQL injection in IceHRM 35.0.0 and 35.0.1 affecting an employee attendance report endpoint. An authenticated remote user may manipulate the employeeList argument to impact database confidentiality, integrity, and availability. Public exploit information is reported, but no confirmed active exploitation is cited.
Executive priority
Treat as a near-term remediation item for any affected IceHRM deployment. The issue involves HR data and has public exploit information, but current sources indicate authentication is required and do not confirm active exploitation.
Technical view
The flaw is in core/src/Reports/User/Reports/EmployeeAttendanceReport.php within the UserReport Endpoint. VulDB describes improper neutralization in data query logic, mapped to CWE-89 and CWE-74. CVSS v2 is 6.5 with network access, low complexity, and single authentication required.
Likely exposure
Organizations running IceHRM 35.0.0 or 35.0.1 are potentially exposed, especially where authenticated users can reach the UserReport endpoint. Exposure is lower if IceHRM is not deployed, is on other versions, or access is tightly restricted.
Exploitation context
The source states the attack can be launched remotely and that exploit material has been published. KEV is false, and the provided sources do not confirm active exploitation in the wild. Authentication is required per the CVSS vector.
Researcher notes
Evidence is primarily from VulDB and the public GitHub issue reference. The vendor reportedly had not responded at publication time, and no official patch or mitigation is named in the provided sources. Avoid assuming broader version impact beyond 35.0.0 and 35.0.1.
Mitigation direction
Check IceHRM vendor and project guidance for an official fix or workaround.
Restrict IceHRM access to trusted users and networks where feasible.
Limit access to reporting functions to users with a business need.
Monitor the GitHub issue and VulDB entry for remediation updates.
Review database and application monitoring for abnormal report activity.
Validation and detection
Inventory IceHRM deployments and confirm versions.
Identify systems running IceHRM 35.0.0 or 35.0.1.
Confirm whether the UserReport endpoint is reachable by authenticated users.
Review logs for EmployeeAttendanceReport.php and employeeList activity.
Track vendor response and retest after applying any official update.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
4CVSS vectors
6Timeline events
0ADP providers
6Source links
CVSS vector scores
4 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-74 · source CWE mapping
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.