Skip to main content
CVE-2024-41368VulnerabilityPublished Updated

CVE-2024-41368: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Aug 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

AI-suggested

1. Immediately restrict network access to the vulnerable PHP script by implementing firewall rules or network segmentation to limit exposure to trusted hosts only. 2. Disable or remove the htdocs\inc.setWlanIpMail.php script if it is not essential for your deployment. 3. Monitor network traffic and system logs for unusual activity or signs of exploitation attempts targeting this script. 4. Apply strict input validation and sanitization if custom modifications are made to the software before an official patch is available. 5. Regularly check for updates or patches from the RPi-Jukebox-RFID maintainers and apply them promptly once released. 6. Consider deploying intrusion detection/prevention systems (IDS/IPS) that can detect exploitation attempts targeting this vulnerability. 7. Educate users and administrators about the risks of exposing Raspberry Pi devices and related services directly to untrusted networks. 8. Implement network-level authentication or VPN access controls to limit remote access to the device. 9. Backup device configurations and data regularly to enable recovery in case of compromise.

Description

RPi-Jukebox-RFID v2.7.0 was discovered to contain a remote code execution (RCE) vulnerability via htdocs\inc.setWlanIpMail.php

References

Community reviews

Loading reviews…