# CVE-2025-70831: Command injection in n/a

> Unauthenticated attackers can execute arbitrary OS commands via the mediaId parameter in rescan.php, leading to full server compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 20 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-pfgm-6983-f589

## What is CVE-2025-70831?

CVE-2025-70831 is a critical command injection vulnerability in n/a, published on 20 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Remote Code Execution (RCE) vulnerability was found in Smanga 3.2.7 in the /php/path/rescan.php interface. The application fails to properly sanitize user-supplied input in the mediaId parameter before using it in a system shell command. This allows an unauthenticated attacker to inject arbitrary operating system commands, leading to complete server compromise.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Lkw199711 Smanga.

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

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

## Is CVE-2025-70831 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-70833](https://insights.sbomify.com/CVE-2025-70833/): Auth bypass in n/a (critical 9.4)
- [CVE-2024-34193](https://insights.sbomify.com/CVE-2024-34193/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-70831 is a critical command injection vulnerability in n/a, published on 20 Feb 2026. 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-70831 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-70831/ (Markdown: https://insights.sbomify.com/CVE-2025-70831/index.md)
```

## Sources

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

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