# CVE-2025-63951: Deserialization in n/a

> Remote unauthenticated attackers can cause denial of service by injecting malicious PHP objects via the rss parameter in the RPi-Jukebox-RFID project.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2025
- **Updated:** 18 Dec 2025
- **Also known as:** GHSA-3cw3-x2fm-86wj

## What is CVE-2025-63951?

CVE-2025-63951 is a high-severity unsafe deserialization vulnerability in n/a, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An insecure deserialization vulnerability exists in the rss-mp3.php script of the MiczFlor RPi-Jukebox-RFID project through commit 4b2334f0ae0e87c0568876fc41c48c38aa9a7014 (2025-10-07). The 'rss' GET parameter receives data that is passed directly to the unserialize() function without validation. This allows a remote, unauthenticated attacker to inject arbitrary PHP objects, causing the application to process them and leading to errors or a denial of service.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2025-63951?

It affects 1 product.


Products: Sourcefabric Phoniebox.

## How do I fix CVE-2025-63951?

No fix has been published for CVE-2025-63951 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-63951 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63951 exists.

## Other vulnerabilities in n/a

- [CVE-2024-41361](https://insights.sbomify.com/CVE-2024-41361/): Code injection in n/a (critical 9.8)
- [CVE-2024-41364](https://insights.sbomify.com/CVE-2024-41364/): Code injection in n/a (critical 9.8)
- [CVE-2024-41366](https://insights.sbomify.com/CVE-2024-41366/): Code injection in n/a (critical 9.8)
- [CVE-2024-41367](https://insights.sbomify.com/CVE-2024-41367/): Code injection in n/a (critical 9.8)
- [CVE-2024-41368](https://insights.sbomify.com/CVE-2024-41368/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-63951 and fix it if it is affected.

What it is: CVE-2025-63951 is a high-severity unsafe deserialization vulnerability in n/a, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63951 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-63951/ (Markdown: https://insights.sbomify.com/CVE-2025-63951/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-63951
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-63951
- OSV: https://osv.dev/vulnerability/CVE-2025-63951

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-63951/
Summaries are generated and may contain mistakes; the official description above is the record.