CVE-2026-53932: Wnx/laravel backup restore Laravel-backup-restore Has An OS Command Vulnerability

HIGH
Advisory Identifier: GHSA-w9mx-xmg4-gc4r
Share
CVSS 8.0
CWE-78 CWE-77
Published
Advisory Summary

CVE-2026-53932 is a HIGH (CVSS 8.0) laravel-backup-restore has an os command vulnerability (CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')) affecting Wnx/laravel backup restore libraries in the Packagist ecosystem. The issue involves laravel-backup-restore has an os command injection during database restore. Remediation is available by upgrading affected packages to version 1.9.4.

CVE-2026-53932 at a Glance

CVE Identifier CVE-2026-53932
GHSA Identifier GHSA-w9mx-xmg4-gc4r
Severity HIGH
CVSS v3.1 Base Score 8.0
CWE Classification CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Affected Product Wnx/laravel backup restore
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 8.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-53932

To remediate this vulnerability, upgrade all affected Wnx/laravel backup restore dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

wnx/laravel-backup-restore fixed: 1.9.4 
Upgrade wnx/laravel-backup-restore to 1.9.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for wnx/laravel-backup-restore

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-53932, inspect your project dependencies for Wnx/laravel backup restore:

inspect dependencies for wnx/laravel-backup-restore

Analyze the terminal output to locate any version of Wnx/laravel backup restore in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.9.4), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'), where the product constructs all or part of an os command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended os command when it is sent to a downstream component. In Wnx/laravel backup restore, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary A crafted backup archive can trigger OS command injection during database restore. The restore workflow extracts a ZIP archive, enumerates files under `db-dumps`, converts the dump path to an absolute path, and passes that path into database import commands that are built as shell command strings. The dump filename is not shell-escaped before it is interpolated into commands such as: - `mysql ... < {dumpFile}` - `gunzip -c {dumpFile}` / `gunzip < {dumpFile}` - `psql ... < {dumpFile}` - `sqlite3 ... < {dumpFile}` Because `Illuminate\Support\Facades\Process::run(string)` uses Symfony `Process::fromShellCommandline()`, shell metacharacters in the dump filename are interpreted by `/bin/sh` on Unix-like systems or by the platform shell on Windows. ### Impact If an attacker can cause an operator or automation to restore a malicious backup archive, the attacker can execute arbitrary shell commands as the PHP/Laravel application user on the system performing the restore. This can lead to application compromise, database credential disclosure, tampering with restored data, and further lateral movement depending on deployment permissions. This is not about malicious SQL inside the dump. The command injection is carried in the ZIP entry filename under `db-dumps`, before the dump content is imported. ### Patches The vulnerability has been fixed in v1.9.4 of the package. ### Workarounds There is no configuration option that disables the vulnerable code path. Upgrading to the patched release is the only complete fix.

CVE-2026-53932 Affected Wnx/laravel backup restore Versions

1 component(s)
Fixed Versions:
1.9.4
Product / Package Ecosystem Affected Versions Fixed Version
wnx/laravel-backup-restore
 Packagist
< 1.9.4
1.9.4

References

GitHub Advisory / Wiki ADVISORY
https://github.com/stefanzweifel/laravel-backup-restore/security/advisories/GHSA-w9mx-xmg4-gc4r
Wnx/laravel backup restore Source Repository REPOSITORY
https://github.com/stefanzweifel/laravel-backup-restore

Frequently Asked Questions

What is CVE-2026-53932?
CVE-2026-53932 is a security vulnerability in Wnx/laravel backup restore involving laravel-backup-restore has an OS Command Injection during database restore under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection').
Which Wnx/laravel backup restore versions are affected?
Affected versions include releases prior to 1.9.4 across affected packages: wnx/laravel-backup-restore.
What version fixes CVE-2026-53932?
Upgrading to 1.9.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is wnx/laravel-backup-restore affected?
Yes, wnx/laravel-backup-restore is affected in releases prior to 1.9.4. Upgrade your dependency to 1.9.4 or later.
What is the CVSS score of CVE-2026-53932?
CVE-2026-53932 has a CVSS v3.1 base score of 8.0 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-53932?
CVE-2026-53932 is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') (The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.).
How can I check Packagist dependencies for CVE-2026-53932?
Run the dependency tree command: 'inspect dependencies for wnx/laravel-backup-restore'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-w9mx-xmg4-gc4r",
  "modified" : "2026-07-09T20:52:57Z",
  "published" : "2026-07-09T20:52:57Z",
  "aliases" : [ "CVE-2026-53932" ],
  "summary" : "laravel-backup-restore has an OS Command Injection during database restore",
  "details" : "## Summary\nA crafted backup archive can trigger OS command injection during database restore. The restore workflow extracts a ZIP archive, enumerates files under `db-dumps`, converts the dump path to an absolute path, and passes that path into database import commands that are built as shell command strings.\n\nThe dump filename is not shell-escaped before it is interpolated into commands such as:\n\n- `mysql ... < {dumpFile}`\n- `gunzip -c {dumpFile}` / `gunzip < {dumpFile}`\n- `psql ... < {dumpFile}`\n- `sqlite3 ... < {dumpFile}`\n\nBecause `Illuminate\\Support\\Facades\\Process::run(string)` uses Symfony `Process::fromShellCommandline()`, shell metacharacters in the dump filename are interpreted by `/bin/sh` on Unix-like systems or by the platform shell on Windows.\n\n### Impact\nIf an attacker can cause an operator or automation to restore a malicious backup archive, the attacker can execute arbitrary shell commands as the PHP/Laravel application user on the system performing the restore. This can lead to application compromise, database credential disclosure, tampering with restored data, and further lateral movement depending on deployment permissions.\n\nThis is not about malicious SQL inside the dump. The command injection is carried in the ZIP entry filename under `db-dumps`, before the dump content is imported.\n\n### Patches\nThe vulnerability has been fixed in v1.9.4 of the package.\n\n### Workarounds\nThere is no configuration option that disables the vulnerable code path. Upgrading to the patched release is the only complete fix.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "wnx/laravel-backup-restore"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.9.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.9.3"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/stefanzweifel/laravel-backup-restore/security/advisories/GHSA-w9mx-xmg4-gc4r"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/stefanzweifel/laravel-backup-restore"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-77", "CWE-78" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-09T20:52:57Z",
    "nvd_published_at" : null
  }
}