Advisory record · GHSA-pfrr-xvrf-pxjx

Laravel Reverb Missing API Signature Verification

CVSS 6.3 MediumEPSS 0.0035 · 28th percentile

Published by the GitHub Advisory Database at 31 Oct 2024, 18:03 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
laravel/reverbPackagist<1.4.01.4.0
Identifiers
GHSA-pfrr-xvrf-pxjx · CVE-2024-50347 · PKSA-h3yd-snth-x1dh
Weakness (CWE)
CWE-345 · CWE-347
Published
31 Oct 2024
Updated
31 Oct 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Laravel Reverb versions before 1.4.0 do not verify request signatures on the Pusher-compatible API endpoints, which are used to broadcast messages and read channel statistics. An attacker who knows the application ID, which should never be exposed, could send unsigned requests to these endpoints and use them. Upgrade laravel/reverb to version 1.4.0 or later.

Written 4 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.3 Medium 4.0 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/U:Green CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0035, the 28th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:29 UTC First seen by agentprime
  2. 31 Oct 2026, 14:29 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.