dbcve.org
Rpi Jukebox RfidApplication · Sourcefabric

CVE-2025-10326

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-12
Fix available
A fix is available. Upgrade to after 2.8.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security flaw has been discovered in MiczFlor RPi-Jukebox-RFID up to 2.8.0. Affected is an unknown function of the file /htdocs/api/playlist/single.php. Performing manipulation of the argument playlist results in os command injection. The attack can be initiated remotely. The exploit has been released to the public and may be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Critical OS command injection vulnerability in RPi-Jukebox-RFID up to v2.8.0. The /htdocs/api/playlist/single.php endpoint fails to sanitize the 'playlist' parameter before passing it to a system call, allowing remote attackers to execute arbitrary operating system commands.

MitigationImmediately restrict network access to the affected API endpoint. Implement proper input validation and use parameterized command execution methods (avoid shell_exec, exec, passthru, system) or parameterized queries to eliminate the injection vector.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Rpi Jukebox RfidApplication
Affected:<= 2.8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate RPi-Jukebox-RFID installation
    Search for the installation directory: look for 'RPi-Jukebox-RFID' folder in common paths such as /var/www/html/, /home/pi/, or the user's home directory. Check for the presence of 'htdocs' subfolder which contains the web application files.
    Affected if The software is not found or the htdocs directory does not exist.
  2. Identify installed version
    Check for a version file in the installation root - look for files named 'version', 'VERSION', or 'version.txt'. Alternatively, search PHP files for version strings like '$version = ' or similar declarations. Compare the found version against the affected range: any version <= 2.8.0 is vulnerable.
    Affected if Installed version is 2.8.0 or lower, or no version file is found but the software is present.
  3. Verify vulnerable script exists
    Check if the file /htdocs/api/playlist/single.php exists within the installation directory. If found, inspect the file for the 'playlist' parameter handling - look for patterns like $_GET['playlist'] or $_POST['playlist'] being used in shell execution functions.
    Affected if The single.php file exists and handles the playlist parameter without sanitization.
  4. Assess network accessibility of API endpoint
    Determine if the web server exposes the /htdocs/api/playlist/single.php endpoint to network access. Check web server configuration for routing to the htdocs folder, and verify whether the API is reachable from external or untrusted networks.
    Affected if The API endpoint is accessible from the network and the software version is <= 2.8.0.

The environment is affected if RPi-Jukebox-RFID version 2.8.0 or lower is installed, the vulnerable single.php script exists, and the API endpoint is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.8.0
Interim mitigation

Immediately restrict network access to the affected API endpoint. Implement proper input validation and use parameterized command execution methods (avoid shell_exec, exec, passthru, system) or parameterized queries to eliminate the injection vector.

Recommended fix Moderate confidence

Latest release newer than 2.8.0 (check GitHub releases for post-2.8.0 version with security fix)

  1. 1. Check the current installed version of RPi-Jukebox-RFID on your system
  2. 2. Visit the official GitHub repository (github.com/MiczFlor/RPi-Jukebox-RFID) to identify the latest available release
  3. 3. If a version newer than 2.8.0 is available, review the release notes to confirm the command injection vulnerability has been fixed
  4. 4. Backup your existing RPi-Jukebox installation including configuration files and audio files
  5. 5. Upgrade to the latest available release using the project's recommended installation method (typically via git pull or reinstall script)
  6. 6. Verify the upgrade was successful by checking the version and testing basic functionality
  7. 7. If no newer version exists or the vendor has not provided a patch, manually fix the vulnerability in /htdocs/api/playlist/single.php by: adding input validation/sanitization for the 'playlist' parameter, using parameterized queries or prepared statements instead of shell_exec/system passthru, escaping shell metacharacters before any command execution, or implementing allowlist validation for pl
Caveat Review release notes for any breaking changes between current version and upgrade target; backup before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rpi Jukebox Rfid Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10326 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10326 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data