CVE-2026-4019 MEDIUM

CVE-2026-4019: Complianz – GDPR/CCPA Cookie Consent <= 7.4.5 - Missing Authorization to Unauthenticated Private Post Content Disclosure via Consent Area REST Endpoint

Vendor Complianz
Product Complianz – GDPR/CCPA Cookie Consent
Weakness CWE-862 · Missing authorization
Published April 29, 2026
Last update April 29, 2026

CVSS base score

5.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality Low
Integrity None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Complianz – GDPR/CCPA Cookie Consent versions 7.4.5 and earlier lack proper authorization checks, allowing unauthenticated attackers to read sensitive data. The vulnerability requires only network access and no user interaction. Site administrators should update to a version newer than 7.4.5 to prevent unauthorized information disclosure.

What an attacker can do

03Attacker Capabilities

Read sensitive data without authentication.

Potential impact on your site

04Site Impact

Unauthorized users can access sensitive information stored or processed by the plugin.

Conditions required to exploit

05Prerequisites

Network access only; no authentication or user interaction required.

Key dates

06Disclosure timeline

April 29, 2026 CVE published
April 29, 2026 Record updated

Related vulnerabilities

08Related CVE