CVE-2025-10370VulnerabilityPublished 13 Sep 2025Updated 3 Feb 2026

CVE-2025-10370: MiczFlor RPi-Jukebox-RFID · Cross Site Scripting

Affects MiczFlor RPi-Jukebox-RFIDSource CVE Database V5

Not known to be exploited · public exploit available (Exploit-DB) · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 13 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
1 Exploit-DB entry, 142 days after disclosure
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by VulDB
2025-09-1214:04Z, 27 hours before disclosure
CVE published
on cve.org
2025-09-1317:02Z, t = 0
In Threat Radar
record ingested
2025-09-1317:15Z, 13 minutes after disclosure
First Exploit-DB entry (opens in a new tab)
RPi-Jukebox-RFID 2.8.0 - Stored Cross-Site Scripting (XSS)
2026-02-02, 142 days after disclosure

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-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
MiczFlor RPi-Jukebox-RFID	Affected =2.0 =2.1 =2.2 =2.3 =2.4 =2.5 =2.6 =2.7 =2.8.0	Fixed in–

AI-suggested

1. Immediately restrict access to the RPi-Jukebox-RFID web interface by network segmentation or firewall rules to limit exposure to trusted users only. 2. Disable or remove the functionality that allows users to input or execute custom scripts until a patch is available. 3. Implement strict input validation and output encoding on the 'Custom script' parameter to neutralize malicious payloads. 4. Educate users about the risks of clicking untrusted links or interacting with unknown web content related to the jukebox interface. 5. Monitor logs for suspicious activity indicative of XSS exploitation attempts. 6. If possible, deploy web application firewalls (WAFs) with rules targeting common XSS attack patterns on the affected endpoints. 7. Regularly check for vendor updates or community patches and apply them promptly once available. 8. Consider isolating the Raspberry Pi devices running this software from critical networks to reduce potential lateral movement. 9. Backup configuration and data regularly to enable recovery in case of compromise. 10. Engage with the open-source community to track developments and share mitigation strategies.

Description

A vulnerability was identified in MiczFlor RPi-Jukebox-RFID up to 2.8.0. This vulnerability affects unknown code of the file /htdocs/userScripts.php. The manipulation of the argument Custom script leads to cross site scripting. The attack is possible to be carried out remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, the impact of CVE-2025-10370 is primarily on confidentiality and integrity within the affected RPi-Jukebox-RFID web interface. Attackers can exploit the XSS vulnerability to hijack user sessions, steal cookies or credentials, or perform unauthorized actions on behalf of legitimate users. While the affected software is niche and typically used in non-critical environments, organizations using it in public or semi-public settings risk reputational damage and potential lateral movement if attackers leverage the compromised device as a foothold. The vulnerability could also be used as a vector for social engineering attacks targeting users interacting with the jukebox interface. Given the lack of vendor response and patch, the risk remains until mitigations are applied. The medium CVSS score reflects moderate impact and exploitability, but the scope is limited to systems running the vulnerable software. European entities involved in education, maker communities, or small businesses using Raspberry Pi-based jukebox solutions should be particularly vigilant.

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Feb 2026, 08:23 UTC

Public exploits and detection1 Exploit-DB entry

Technical details

References

Community reviews

Related threats