# Livewire DOM-based cross-site scripting during client-side state handling Advisory record · `GHSA-g3hc-697w-wm82` - **Identifiers:** `GHSA-g3hc-697w-wm82` · `CVE-2026-81887` · `PKSA-bgw4-5zmg-2njg` - **State:** Confirmed - **Severity:** CVSS 5.1 Medium - **Critical:** No - **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html) · [CWE-1321](https://cwe.mitre.org/data/definitions/1321.html) - **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md) · [Prototype pollution](https://agentprime.io/advisories/tag/prototype-pollution.md) - **Published:** 2 Sept 2026 - **Updated:** 2 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 2 Sept 2026, 14:38 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `livewire/livewire` (Packagist): affected `>=3.0.0-beta.1, <3.8.3 || >=4.0.0-beta.1, <4.3.4`; fixed in `3.8.3`, `4.3.4` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Livewire, the PHP full-stack framework, is vulnerable to DOM-based cross-site scripting in versions 3.0.0-beta.1 up to 3.8.2 and 4.0.0-beta.1 up to 4.3.3, caused by how certain client-side component state is handled. An unauthenticated attacker can run arbitrary JavaScript in the origin of an affected application, but only in specific scenarios and only if a user interacts with the attacker's content. The source says the issue does not bypass server-side authorisation. Upgrade to Livewire 3.8.3 or 4.3.4, which fix the problem; the source lists no workaround. Written 31 Oct 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 - 5.1 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0068, the 53rd percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 10 Aug 2026, 23:31 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/livewire/livewire/security/advisories/GHSA-g3hc-697w-wm82) - 31 Oct 2026, 14:06 UTC: First seen by agentprime - 31 Oct 2026, 14:06 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-g3hc-697w-wm82) ## Sources - [GitHub Advisory Database: GHSA-g3hc-697w-wm82](https://github.com/advisories/GHSA-g3hc-697w-wm82) - [OSV: GHSA-g3hc-697w-wm82](https://osv.dev/vulnerability/GHSA-g3hc-697w-wm82) - - - - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .