Is laravel/socialite 2.0 vulnerable?

Composer · 23 releases from 2.0.0 to 2.0.22 · latest laravel/socialite is 5.31.0 · checked 1 Nov 2026

No known advisories in the last release

laravel/socialite 2.0.22, the last 2.0 release, has no known advisories. 2 advisories affect earlier 2.0.x releases, so update to 2.0.22.

Update within 2.0:composer require laravel/socialite:^2.0.22

Is your project affected?

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

Fixed within 2.0.x, affecting earlier releases

  • MediumGHSA-h97c-qp24-439v15 May 2024

    Insecure State Generation in laravel/socialite

    Affected
    >=1.0.0 <2.0.9
    Fixed in
    2.0.9
  • MediumGHSA-7fjv-25q9-2w8815 May 2024

    State Guessing Vulnerability in laravel/socialite

    Affected
    >=1.0.0 <2.0.10
    Fixed in
    2.0.10

Which of your client projects are still on laravel/socialite 2.0?

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

Scan a project free, no signupOr connect GitHub to scan every repo

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