Skip to main content
VulnerabilityPublished

CVE-2024-46073: IceHRM · Cross-site Scripting

Source CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate this vulnerability, organizations should implement the following specific measures: 1) Apply strict input validation and output encoding on the 'next' parameter to ensure all user-supplied data is properly escaped before reflection in the response. 2) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in the browser context. 3) Educate users to be cautious about clicking on suspicious or unsolicited URLs, especially those purporting to redirect within the IceHRM login page. 4) Monitor web server logs for unusual or suspicious requests containing script payloads in the 'next' parameter. 5) If possible, temporarily disable or restrict the use of the 'next' parameter until a vendor patch is released. 6) Engage with IceHRM support or community channels to obtain updates or patches addressing this issue. 7) Consider implementing web application firewalls (WAFs) with rules to detect and block reflected XSS attempts targeting the login page. These targeted mitigations go beyond generic advice by focusing on the specific vulnerable parameter and the context of the application.

Description

A reflected Cross-Site Scripting (XSS) vulnerability exists in the login page of IceHRM v32.4.0.OS. The vulnerability is due to improper sanitization of the "next" parameter, which is included in the application's response without adequate escaping. An attacker can exploit this flaw by tricking a user into visiting a specially crafted URL, causing the execution of arbitrary JavaScript code in the context of the victim's browser. The issue occurs even though the application has sanitization mechanisms in place.

References

Community reviews

Loading reviews…