VulnerabilityPublished 13 Sep 2025Updated 15 Sep 2025

CVE-2025-10369: MiczFlor RPi-Jukebox-RFID · Cross-site Scripting

Affects MiczFlor RPi-Jukebox-RFIDSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score

5.1Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% 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

Disclosed: evidence found.
CVE published 13 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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

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.

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

Given the absence of official patches, European organizations should implement the following specific mitigations: 1) Restrict network access to the RPi-Jukebox-RFID web interface by using firewalls or VPNs to limit exposure to trusted users only. 2) Employ web application firewalls (WAFs) with custom rules to detect and block typical XSS payloads targeting the /htdocs/cardRegisterNew.php endpoint. 3) Disable or restrict user input fields related to card registration if not actively used, or implement manual input validation and sanitization at the network perimeter. 4) Monitor logs for unusual input patterns or repeated access attempts to the vulnerable page. 5) Educate users about the risks of clicking untrusted links related to the device’s web interface. 6) Consider isolating the device on a segmented network to prevent potential lateral movement. 7) Explore alternative software solutions or versions without this vulnerability if feasible. 8) Regularly check for vendor updates or community patches addressing this issue.

Description

A vulnerability was determined in MiczFlor RPi-Jukebox-RFID up to 2.8.0. This affects an unknown part of the file /htdocs/cardRegisterNew.php. Executing manipulation can lead to cross site scripting. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, the impact of this vulnerability depends largely on the deployment scale and context of RPi-Jukebox-RFID usage. While primarily a hobbyist or small business tool, organizations using this software for public or semi-public music playback could face reputational damage if attackers exploit the XSS to deface interfaces or deliver malicious payloads to users. In environments where the device interfaces with broader internal networks, the XSS could be a stepping stone for further attacks, such as phishing or lateral movement, especially if combined with other vulnerabilities. Confidentiality impact is limited, but integrity and user trust can be compromised. Since the vulnerability requires user interaction, the risk is somewhat mitigated, but the ease of remote exploitation and lack of vendor response increase concern. European organizations with public-facing installations or those in sectors like hospitality, education, or retail using RPi-Jukebox-RFID should be particularly cautious.

Summary

CVE-2025-10369 is a cross-site scripting (XSS) vulnerability identified in the MiczFlor RPi-Jukebox-RFID software versions up to 2.8.0. The vulnerability exists in the /htdocs/cardRegisterNew.php file, where insufficient input sanitization allows an attacker to inject malicious scripts. This flaw can be exploited remotely without authentication, requiring only partial user interaction, such as visiting a crafted URL or submitting manipulated input. The vulnerability has a CVSS 4.0 base score of 5.1, indicating a medium severity level. The attack vector is network-based (AV:N), with low attack complexity (AC:L), no privileges required (PR:L interpreted as low privileges), and user interaction needed (UI:P). The impact primarily affects the integrity of the web interface, with limited impact on confidentiality and availability. The vendor was notified but did not respond, and no patches or mitigations have been published yet. Although no known exploits are currently in the wild, public disclosure increases the risk of exploitation. The RPi-Jukebox-RFID is a niche open-source project designed for Raspberry Pi devices to manage music playback via RFID cards, often used in hobbyist or small-scale environments. The vulnerability could allow attackers to execute arbitrary JavaScript in the context of the affected web application, potentially leading to session hijacking, defacement, or redirection to malicious sites.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Sep 2025, 00:38 UTC

Technical details

References

Community reviews

Related threats