Skip to main content
Vulnerability Database/CVE-2025-10370

CVE-2025-10370: RPi-Jukebox-RFID XSS Vulnerability

CVE-2025-10370 is a cross-site scripting flaw in MiczFlor RPi-Jukebox-RFID that enables attackers to inject malicious scripts through the Custom script parameter. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-10370 Overview

CVE-2025-10370 is a cross-site scripting (XSS) vulnerability [CWE-79] affecting MiczFlor RPi-Jukebox-RFID versions up to 2.8.0. The flaw resides in /htdocs/userScripts.php, where the Custom script argument accepts unsanitized input. An authenticated remote attacker can inject arbitrary JavaScript that executes in the context of other users' browsers. A public proof-of-concept is available on GitHub and Exploit-DB. The vendor was contacted prior to disclosure but did not respond.

Critical Impact

Authenticated attackers can inject persistent JavaScript into the RPi-Jukebox web interface, enabling session hijacking, credential theft, and unauthorized actions through victim browsers.

Affected Products

  • MiczFlor RPi-Jukebox-RFID versions up to and including 2.8.0
  • The vulnerable component is /htdocs/userScripts.php
  • The affected parameter is the Custom script input field

Discovery Timeline

  • 2025-09-13 - CVE-2025-10370 published to NVD
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2025-10370

Vulnerability Analysis

The vulnerability exists in the userScripts.php endpoint of the RPi-Jukebox-RFID web interface. The Custom script parameter is reflected or stored without proper output encoding or input sanitization. When a user visits the affected page, injected payloads execute within the browser session of the authenticated user.

Exploitation requires low privileges and some user interaction, but the attack originates over the network. The impact is limited to the browser context of users who load the manipulated page. Possible consequences include session token theft, defacement of the jukebox administrative interface, and client-side request forgery against the application.

A public proof-of-concept is hosted at the GitHub PoC repository and referenced in Exploit-DB entry 52470. Additional details are tracked in VulDB entry 323778.

Root Cause

The root cause is improper neutralization of input during web page generation [CWE-79]. The application accepts user-controlled data in the Custom script field and renders it in HTML output without applying context-appropriate encoding such as HTML entity escaping or JavaScript string encoding.

Attack Vector

An attacker with valid low-privilege access to the RPi-Jukebox-RFID interface submits a crafted payload to /htdocs/userScripts.php via the Custom script parameter. When another authenticated user loads the affected view, the injected script executes in their browser. Full exploitation details are documented in the public PoC.

Detection Methods for CVE-2025-10370

Indicators of Compromise

  • HTTP POST or GET requests to /htdocs/userScripts.php containing <script>, onerror=, onload=, or javascript: substrings in the Custom script parameter
  • Unexpected JavaScript or HTML markup appearing in stored user scripts within the jukebox web interface
  • Browser console errors or unusual outbound requests triggered when loading the user scripts page

Detection Strategies

  • Inspect web server access logs for requests to userScripts.php with suspicious URL-encoded payloads or HTML tag fragments
  • Deploy a web application firewall (WAF) with XSS signature rules in front of the Raspberry Pi web interface
  • Perform periodic review of stored scripts in the jukebox database or configuration files for embedded HTML or JavaScript

Monitoring Recommendations

  • Enable verbose access logging on the Apache or Nginx server fronting the RPi-Jukebox application
  • Correlate authentication events with modifications to user scripts to identify abusive accounts
  • Monitor browser telemetry on management workstations used to administer the jukebox for anomalous script execution

How to Mitigate CVE-2025-10370

Immediate Actions Required

  • Restrict network access to the RPi-Jukebox-RFID web interface by binding it to a trusted LAN segment or placing it behind a VPN
  • Audit existing user accounts and remove or rotate credentials for any shared or weak logins
  • Review stored custom scripts and remove any entries containing HTML tags or JavaScript

Patch Information

No vendor-supplied patch is referenced in the NVD data at the time of disclosure. The vendor did not respond to coordinated disclosure attempts. Users of versions up to 2.8.0 should monitor the MiczFlor RPi-Jukebox-RFID project for updates and apply fixes as soon as they become available.

Workarounds

  • Place the jukebox interface behind an authenticating reverse proxy that filters HTML and JavaScript metacharacters in POST bodies
  • Configure a strict Content Security Policy (CSP) header to block inline script execution in the browser
  • Disable or restrict access to the userScripts.php endpoint if the custom scripts feature is not required in the deployment
bash
# Example Nginx snippet to add a restrictive CSP and limit access to userScripts.php
location /htdocs/userScripts.php {
    allow 192.168.1.0/24;
    deny all;
    add_header Content-Security-Policy "default-src 'self'; script-src 'self'; object-src 'none'" always;
    add_header X-XSS-Protection "1; mode=block" always;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.