dbcve.org
InjectionWeakness · CWE-74

CVE-2026-15478

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in IceHRM up to version 35.0.1 in the EmployeeAttendanceReport.php file. The employeeList parameter passed to the UserReport endpoint is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL commands.

MitigationImplement prepared statements/parameterized queries for all SQL operations involving the employeeList parameter. Alternatively, apply any available vendor patch or upgrade to a version beyond 35.0.1. Perform input validation and employ least-privilege database accounts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm IceHRM installation and version
    Locate the IceHRM installation directory on the server; check for version.php, VERSION file, or the admin panel under System > Version Info to identify the installed version number
    Affected if Installed version is 35.0.1 or below
  2. Locate the vulnerable PHP file
    Search for EmployeeAttendanceReport.php within the IceHRM web directory structure, typically found under /src/ or /modules/ folders
    Affected if EmployeeAttendanceReport.php file exists in the installation
  3. Verify UserReport endpoint is accessible
    Check if the web application exposes the UserReport functionality (look for routes or links containing UserReport in the application)
    Affected if UserReport endpoint or module is accessible via the web interface
  4. Inspect employeeList parameter handling
    Review the source code of EmployeeAttendanceReport.php and locate where the employeeList parameter is used in SQL queries; check if it is directly concatenated into the query string without prepared statements or parameter binding
    Affected if The employeeList parameter is used in SQL queries without prepared statements or input sanitization

Environment is affected if running IceHRM version 35.0.1 or below with the EmployeeAttendanceReport.php file present and the employeeList parameter being passed directly into SQL queries without parameterized binding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement prepared statements/parameterized queries for all SQL operations involving the employeeList parameter. Alternatively, apply any available vendor patch or upgrade to a version beyond 35.0.1. Perform input validation and employ least-privilege database accounts.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15478 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15478 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data