Is wnx/laravel-backup-restore 0.3 vulnerable?

Composer · 2 releases from 0.3.0 to 0.3.1 · latest wnx/laravel-backup-restore is 2.1.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. wnx/laravel-backup-restore 0.3.1, the last 0.3 release, is affected by 1 known security advisory (1 high), including CVE-2026-53932. Upgrade to 1.9.4 or later to fix all of them.

Upgrade with:composer require wnx/laravel-backup-restore:^1.9.4

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

Advisories affecting wnx/laravel-backup-restore 0.3.1

  • 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 0.3.x release

Affected: 0.3.0 to 0.3.1. Latest wnx/laravel-backup-restore: 2.1.0.

VersionKnown advisories
wnx/laravel-backup-restore 0.3.1CVE-2026-53932
wnx/laravel-backup-restore 0.3.0CVE-2026-53932

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

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.