Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-10369: Cross Site Scripting in MiczFlor RPi-Jukebox-RFID

0
Medium
VulnerabilityCVE-2025-10369cvecve-2025-10369
Published: Sat Sep 13 2025 (09/13/2025, 16:32:06 UTC)
Source: CVE Database V5
Vendor/Project: MiczFlor
Product: RPi-Jukebox-RFID

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.

AI-Powered Analysis

AILast updated: 09/21/2025, 00:38:03 UTC

Technical Analysis

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.

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

Mitigation Recommendations

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.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-09-12T14:04:38.880Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68c59f9ae14ebf9f5cc7511d

Added to database: 9/13/2025, 4:45:14 PM

Last enriched: 9/21/2025, 12:38:03 AM

Last updated: 10/30/2025, 2:09:54 PM

Views: 46

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats