dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-9573

HIGH · 8.6 CVSS v4.0 Published 2025-09-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable 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
The ns_backup extension through 13.0.2 for TYPO3 allows command injection.

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 · moderate confidence

The ns_backup extension for TYPO3 versions through 13.0.2 contains a command injection vulnerability (CWE-78), allowing remote attackers to execute arbitrary OS commands via unspecified vectors in the backup functionality.

MitigationUpdate the ns_backup extension to a patched version beyond 13.0.2, or if no patched version is available, remove the extension from the TYPO3 installation immediately and implement alternative backup solutions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Verify ns_backup extension is installed
    Check TYPO3 extension manager or composer.json for presence of ns_backup extension
    Affected if ns_backup extension is present in the TYPO3 installation
  2. Determine installed ns_backup version
    Check extension version in TYPO3 extension manager, composer.json, or ext_emconf.php file
    Affected if Version is 13.0.2 or any earlier version (versions through 13.0.2 are affected)
  3. Confirm backup functionality is accessible
    Check if the backup module is enabled and accessible in TYPO3 backend under the ns_backup extension menu
    Affected if Backup module is enabled and accessible to users (command injection occurs in backup functionality)
  4. Inspect backup-related configuration
    Review any backup job configurations, scheduled tasks, or custom parameters stored in TYPO3 configuration files or database related to ns_backup
    Affected if Custom parameters or command configurations exist that could be manipulated

User is affected if ns_backup extension version 13.0.2 or earlier is installed AND the backup functionality is accessible in the TYPO3 environment

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the ns_backup extension to a patched version beyond 13.0.2, or if no patched version is available, remove the extension from the TYPO3 installation immediately and implement alternative backup solutions.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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