# CVE-2025-9573: Command Injection in extension "TYPO3 Backup Plus" (ns_backup)

> Attackers can execute arbitrary commands via the TYPO3 Backup Plus extension, requiring an upgrade to mitigate.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2025
- **Updated:** 2 Sep 2025

## What is CVE-2025-9573?

CVE-2025-9573 is a high-severity command injection vulnerability in Extension "TYPO3 Backup Plus", published on 2 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The ns_backup extension through 13.0.2 for TYPO3 allows command injection.

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

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


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

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

## Is CVE-2025-9573 being exploited?

There is no known exploitation of CVE-2025-9573 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9573 is a high-severity command injection vulnerability in Extension "TYPO3 Backup Plus", published on 2 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9573 in the wild and no public exploit code.

Affected product: Extension "TYPO3 Backup Plus". 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-9573/ (Markdown: https://insights.sbomify.com/CVE-2025-9573/index.md)
```

## Sources

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

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