Livewire DOM-based cross-site scripting during client-side state handling
Published 2 Sept 2026 · Updated 2 Sept 2026
Affected packages
- Affected
- >=3.0.0-beta.1 <3.8.3
- Fixed in
- 3.8.3
composer require livewire/livewire:^3.8.3- Affected
- >=4.0.0-beta.1 <4.3.4
- Fixed in
- 4.3.4
composer require livewire/livewire:^4.3.4Details
Impact
In Livewire v3 (≤ 3.8.2) and v4 (≤ 4.3.3), a vulnerability allows unauthenticated attackers to execute arbitrary JavaScript in the origin of an affected application in specific scenarios. The issue stems from how certain client-side component state is handled. This vulnerability does not affect prior major versions. Exploitation requires user interaction, but does not require authentication or prior access to the application. The issue does not bypass server-side authorisation and grants an attacker no privileges beyond those the affected user already holds.
Patches
This issue has been patched in Livewire v3.8.3 and v4.3.4. All users are strongly encouraged to upgrade to these versions or later as soon as possible.
Workarounds
There is no known workaround at this time. Users are strongly advised to upgrade to a patched version immediately.
Is GHSA-g3hc-697w-wm82 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected livewire/livewire, and gives you the command that fixes it.
References
- Linkgithub.com/livewire/livewire/security/advisories/GHSA-g3hc-697w-wm82
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-81887
- Linkgithub.com/livewire/livewire/pull/10467
- Linkgithub.com/livewire/livewire/commit/11ebe646f7e81dde2d714815da8b3019d058561e
- Packagegithub.com/livewire/livewire
- Linkgithub.com/livewire/livewire/releases/tag/v3.8.3
- Linkgithub.com/livewire/livewire/releases/tag/v4.3.4
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.