CVE-2025-48204
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 · uneditedThe ns_backup extension through 13.0.0 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 confidenceThe ns_backup extension for TYPO3 versions through 13.0.0 contains a command injection vulnerability that allows attackers to execute arbitrary operating system commands on the server by supplying malicious input that is improperly handled and passed to system shell execution functions.
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
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify ns_backup extension is installedIn TYPO3 backend, navigate to Extension Manager and search for 'ns_backup', or check the file system for existence of typo3conf/ext/ns_backup/ or vendor/ns_backup/ directoryAffected if The extension directory exists and the extension is loaded in TYPO3
-
Determine installed version of ns_backupCheck the extension version in ext_emconf.php (TYPO3 < 12) or composer.json (TYPO3 12+) within the ns_backup extension directory, or view version via Extension ManagerAffected if Version is 13.0.0 or lower, or version cannot be determined (indicating an unmaintained or outdated release)
-
Confirm backup command functionality is accessibleIdentify if any CLI or web endpoint exists that triggers backup operations - check for console commands registered by the extension (typo3cms command:list | grep backup) or accessible controller actionsAffected if Backup command execution functionality is enabled and exposed
-
Check web server access logs for suspicious requestsReview web server access logs (Apache/nginx) for POST/GET requests to paths containing 'backup', 'ns_backup', or 'execute' that may indicate exploitation attemptsAffected if Malicious payload patterns or unexpected backup-related requests are found in logs
User is affected if ns_backup extension is installed with version 13.0.0 or lower AND the backup command execution feature is accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the ns_backup extension to a patched version once released by the vendor, or disable the extension until a fix is available. If the extension is not actively maintained, consider alternative backup solutions.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48204 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48204 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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