# CVE-2026-4019: Missing authorization in Complianz – GDPR/CCPA Cookie Consent

> Unauthenticated attackers can read private, draft, or unpublished post content via a vulnerable REST API endpoint in the Complianz WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2026
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-648g-qp2w-38qp

## What is CVE-2026-4019?

CVE-2026-4019 is a medium-severity missing authorization vulnerability in Complianz – GDPR/CCPA Cookie Consent, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Complianz – GDPR/CCPA Cookie Consent plugin for WordPress is vulnerable to unauthorized data access in all versions up to, and including, 7.4.5 This is due to the REST API endpoint at /wp-json/complianz/v1/consent-area/{post_id}/{block_id} using __return_true as the permission_callback, allowing any unauthenticated user to access it. The cmplz_rest_consented_content() function retrieves a post by ID via get_post() and returns the consentedContent attribute of any complianz/consent-area block found in it, without checking if the post is published or if the user has permission to read it. This makes it possible for unauthenticated attackers to read the consent area block content from private, draft, or unpublished posts.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-4019?


## How do I fix CVE-2026-4019?

No fix has been published for CVE-2026-4019 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4019 being exploited?

There is no known exploitation of CVE-2026-4019 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4019 and fix it if it is affected.

What it is: CVE-2026-4019 is a medium-severity missing authorization vulnerability in Complianz – GDPR/CCPA Cookie Consent, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4019 in the wild and no public exploit code.

Affected product: Complianz – GDPR/CCPA Cookie Consent. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4019/ (Markdown: https://insights.sbomify.com/CVE-2026-4019/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4019
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4019
- OSV: https://osv.dev/vulnerability/CVE-2026-4019

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4019/
Summaries are generated and may contain mistakes; the official description above is the record.