dbcve.org
Rpi Jukebox RfidApplication · Sourcefabric

CVE-2025-10327

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 weakness has been identified in MiczFlor RPi-Jukebox-RFID up to 2.8.0. Affected by this vulnerability is an unknown functionality of the file /htdocs/api/playlist/shuffle.php. Executing manipulation of the argument playlist can lead to os command injection. The attack can be launched remotely. The exploit has been made available to the public and could 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

A critical OS command injection vulnerability exists in the RPi-Jukebox-RFID application (versions up to 2.8.0) in the /htdocs/api/playlist/shuffle.php endpoint. The 'playlist' parameter is not properly sanitized before being used in system commands, allowing remote attackers to execute arbitrary OS commands.

MitigationUntil a vendor patch is available, implement input validation/sanitization on the playlist parameter in shuffle.php to prevent shell metacharacter injection, or restrict the application's permissions to limit command execution impact.

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 the RPi-Jukebox-RFID installation directory
    Search for the 'htdocs' folder or the 'RPi-Jukebox-RFID' directory on the system. Common paths include /var/www/html/, /home/pi/RPi-Jukebox-RFID/, or the web server document root.
    Affected if The application directory exists on the system
  2. Identify the installed version
    Check for a version file (VERSION, version.php, or similar) in the application root directory, or examine the git tags if it's a git repository. Compare the version number to the affected range (<=2.8.0).
    Affected if The installed version is 2.8.0 or lower, or no version file is found indicating an older installation
  3. Verify the vulnerable shuffle.php file exists
    Inspect the path /htdocs/api/playlist/shuffle.php within the application directory. Confirm the file is present.
    Affected if The file /htdocs/api/playlist/shuffle.php exists in the installation
  4. Check for command injection vulnerability in the playlist parameter
    Review the shuffle.php source code and locate where the 'playlist' parameter is used in shell commands (e.g., exec(), shell_exec(), system(), passthru()). Look for direct insertion of the parameter into system calls without sanitization functions like escapeshellarg().
    Affected if The 'playlist' parameter is passed directly to PHP system functions without input validation or escaping
  5. Determine if the web interface is exposed
    Check the web server configuration (Apache, Nginx) to see if the /htdocs/api/ endpoint is accessible via network. Look for Allow/Deny directives or firewall rules.
    Affected if The /api/playlist/shuffle.php endpoint is accessible over the network (not localhost-only or firewalled)

The system is affected if RPi-Jukebox-RFID version 2.8.0 or lower is installed, the shuffle.php file exists, and the playlist parameter is used in system commands without sanitization, with the API endpoint 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.

From vendor data
Upgrade available Upgrade to a release after 2.8.0
Interim mitigation

Until a vendor patch is available, implement input validation/sanitization on the playlist parameter in shuffle.php to prevent shell metacharacter injection, or restrict the application's permissions to limit command execution impact.

Fix this in Rpi Jukebox Rfid Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10327 — 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-10327 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