dbcve.org
Rpi Jukebox RfidApplication · Sourcefabric

CVE-2025-10328

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 vulnerability has been detected in MiczFlor RPi-Jukebox-RFID up to 2.8.0. Affected by this issue is some unknown functionality of the file /htdocs/api/playlist/playsinglefile.php. The manipulation of the argument File leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. 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

OS command injection vulnerability in RPi-Jukebox-RFID's /htdocs/api/playlist/playsinglefile.php allows remote attackers to execute arbitrary OS commands via the 'File' parameter. The lack of input sanitization on this parameter enables attackers to inject shell commands that are executed on the server with the application's privileges.

MitigationImplement strict input validation on the File parameter, preferably using a whitelist approach to only allow known-good filenames, or use parameterized methods instead of shell commands for file operations. If shell execution is unavoidable, use proper escaping and avoid passing user input directly to system calls.

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
    Identify the web root directory where the application is installed (typically /var/www/html or similar). Look for the presence of the 'htdocs' directory and the overall application structure.
    Affected if The application is not found on the system.
  2. Check installed version
    Examine version.php or any VERSION file in the application root, or check git tags if installed from source. Compare the version number to the affected range (2.8.0 and below).
    Affected if The installed version is 2.8.0 or lower.
  3. Verify vulnerable endpoint exists
    Inspect the file /htdocs/api/playlist/playsinglefile.php in the web root. Confirm the file exists and contains code that processes the 'File' parameter.
    Affected if The file exists and processes the File parameter without apparent sanitization.
  4. Check web service exposure
    Determine if the web interface is accessible (check web server configuration for the application). Note the URL path to the API endpoint.
    Affected if The web service is running and the API endpoint is accessible.
  5. Inspect File parameter handling
    Review the source code of playsinglefile.php to confirm that user input from the 'File' parameter is passed directly to shell execution functions (such as shell_exec, exec, system, or passthru) without sanitization.
    Affected if The code passes the File parameter to shell functions without validation.

The system is affected if RPi-Jukebox-RFID version 2.8.0 or lower is installed, the vulnerable playsinglefile.php endpoint exists, and the File parameter is processed without sanitization before shell execution.

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

Implement strict input validation on the File parameter, preferably using a whitelist approach to only allow known-good filenames, or use parameterized methods instead of shell commands for file operations. If shell execution is unavoidable, use proper escaping and avoid passing user input directly to system calls.

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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