Is wnx/laravel-backup-restore 1.9 vulnerable?

Composer · 8 releases from 1.9.0 to 1.9.7 · latest wnx/laravel-backup-restore is 2.1.0 · checked 18 Nov 2026

No known advisories in the last release

wnx/laravel-backup-restore 1.9.7, the last 1.9 release, has no known advisories. 1 advisory affects earlier 1.9.x releases, so update to 1.9.7.

Update within 1.9:composer require wnx/laravel-backup-restore:^1.9.7

Is your project on an affected wnx/laravel-backup-restore?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 1.9.x, affecting earlier releases

  • HighCVE-2026-53932GHSA-w9mx-xmg4-gc4r9 Jul 2026

    laravel-backup-restore has an OS Command Injection during database restore

    Affected
    <1.9.4
    Fixed in
    1.9.4

Every wnx/laravel-backup-restore 1.9.x release

Affected: 1.9.0 to 1.9.3. 1.9.4 and later are not affected. Latest wnx/laravel-backup-restore: 2.1.0.

VersionKnown advisories
wnx/laravel-backup-restore 1.9.7None
wnx/laravel-backup-restore 1.9.6None
wnx/laravel-backup-restore 1.9.5None
wnx/laravel-backup-restore 1.9.4None
wnx/laravel-backup-restore 1.9.3CVE-2026-53932
wnx/laravel-backup-restore 1.9.2CVE-2026-53932
wnx/laravel-backup-restore 1.9.1CVE-2026-53932
wnx/laravel-backup-restore 1.9.0CVE-2026-53932

Which of your client projects are still on wnx/laravel-backup-restore 1.9?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact wnx/laravel-backup-restore version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other wnx/laravel-backup-restore versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.