Skip to main content
VulnerabilityPublished Updated

CVE-2024-41367: RPi-Jukebox-RFID · Code Injection

Affects RPi-Jukebox-RFIDSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 11:42 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubmiczflor/RPi-Jukebox-RFIDpkg:github/miczflor/RPi-Jukebox-RFIDOther threatsAffected
  • =2.7.0
Fixed in–

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

AI-suggested

Until an official patch is released, organizations should take immediate steps to mitigate the risk posed by CVE-2024-41367. These include: 1) Isolate RPi-Jukebox-RFID devices from untrusted networks by placing them behind firewalls or on segmented VLANs to limit exposure. 2) Restrict access to the appendFileToPlaylist.php API endpoint by implementing network-level controls or web application firewalls (WAFs) that can detect and block suspicious requests. 3) Disable or remove the vulnerable API endpoint if it is not essential for operations. 4) Monitor network traffic and device logs for unusual activity indicative of exploitation attempts. 5) Employ intrusion detection/prevention systems (IDS/IPS) tuned to detect code injection patterns. 6) Educate users and administrators about the vulnerability and encourage minimizing device exposure to public networks. 7) Regularly check for updates from the RPi-Jukebox-RFID project and apply patches promptly once available. 8) Consider deploying application-layer authentication or access controls to restrict API usage. These targeted actions go beyond generic advice by focusing on network segmentation, endpoint hardening, and proactive monitoring specific to the vulnerable component.

Description

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

References

Community reviews

Loading reviews…