Is hhxsv5/laravel-s 1.1 vulnerable?

Composer · 11 releases from 1.1.0 to 1.1.11 · latest hhxsv5/laravel-s is 3.8.8 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. hhxsv5/laravel-s 1.1.11, the last 1.1 release, is affected by 1 known security advisory (1 critical), including CVE-2023-29931. Upgrade to 3.7.36 or later to fix all of them.

Upgrade with:composer require hhxsv5/laravel-s:^3.7.36

Is your project on an affected hhxsv5/laravel-s?

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 hhxsv5/laravel-s 1.1.11

  • CriticalCVE-2023-29931GHSA-q2fp-jw87-86px22 Jun 2023

    laravel-s vulnerable to Local File Inclusion

    Affected
    <3.7.36
    Fixed in
    3.7.36

Every hhxsv5/laravel-s 1.1.x release

Affected: 1.1.0 to 1.1.11. Latest hhxsv5/laravel-s: 3.8.8.

VersionKnown advisories
hhxsv5/laravel-s 1.1.11CVE-2023-29931
hhxsv5/laravel-s 1.1.10CVE-2023-29931
hhxsv5/laravel-s 1.1.9CVE-2023-29931
hhxsv5/laravel-s 1.1.8CVE-2023-29931
hhxsv5/laravel-s 1.1.7CVE-2023-29931
hhxsv5/laravel-s 1.1.6CVE-2023-29931
hhxsv5/laravel-s 1.1.5CVE-2023-29931
hhxsv5/laravel-s 1.1.4CVE-2023-29931
hhxsv5/laravel-s 1.1.2CVE-2023-29931
hhxsv5/laravel-s 1.1.1CVE-2023-29931
hhxsv5/laravel-s 1.1.0CVE-2023-29931

Which of your client projects are still on hhxsv5/laravel-s 1.1?

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

Other hhxsv5/laravel-s 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.