Skip to main content
CVE-2024-41374VulnerabilityPublished Updated

CVE-2024-41374: icecoder · n/a

Affects icecoderSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 25 Oct 2026, 19:02 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 27% 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 26 Jul 2024

  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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubxjzzzxx/icecoderpkg:github/xjzzzxx/icecoderOther threatsAffected
  • =8.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor for official patches or updates from ICEcoder and apply them immediately once available to remediate the vulnerability. 2. Until patches are released, restrict access to the ICEcoder interface, especially the settings screen, to trusted users and networks only. 3. Implement web application firewall (WAF) rules to detect and block suspicious input patterns targeting the vulnerable endpoint. 4. Conduct input validation and output encoding on all user-supplied data within the application, particularly in the settings-screen.php component, to prevent script injection. 5. Educate users about the risks of interacting with untrusted links or inputs that could trigger XSS attacks. 6. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in the browser context. 7. Regularly audit and monitor logs for unusual activity or attempts to exploit this vulnerability. 8. Consider isolating ICEcoder environments or running them in sandboxed containers to limit potential damage from compromise.

Description

ICEcoder 8.1 is vulnerable to Cross Site Scripting (XSS) via lib/settings-screen.php

References

Community reviews

Loading reviews…