dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-4019

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Complianz WordPress plugin exposes a REST API endpoint at /wp-json/complianz/v1/consent-area/{post_id}/{block_id} that uses __return_true as its permission_callback, permitting any unauthenticated user to access it. The cmplz_rest_consented_content() function retrieves posts via get_post() and returns the consentedContent attribute from complianz/consent-area blocks without verifying post publication status or user read permissions, enabling attackers to read content from private, draft, or unpublished posts.

MitigationUpdate the plugin to version 7.4.6 or later which contains proper authorization checks. Alternatively, implement a proper permission_callback function that validates user capabilities and post status before returning content.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Complianz plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Complianz' in the list. Alternatively, check the filesystem at wp-content/plugins/complianz/ for the plugin directory.
    Affected if The Complianz plugin is installed and active in WordPress.
  2. Determine installed plugin version
    In WordPress admin, click on the Complianz plugin to view its details, which displays the version number. Alternatively, check the main plugin file header at wp-content/plugins/complianz/complianz.php for the 'Version' comment.
    Affected if The installed version is earlier than 7.4.6 (the patched version).
  3. Check REST API endpoint accessibility
    Send a GET request to /wp-json/complianz/v1/consent-area/1/test using a tool like curl or a browser (logged out). Example: curl -s https://yourdomain.com/wp-json/complianz/v1/consent-area/1/test
    Affected if The endpoint returns a response without requiring authentication (HTTP 200).
  4. Verify private/draft content is exposed
    Create a private or draft post, then access the REST API endpoint with that post's ID: /wp-json/complianz/v1/consent-area/{post_id}/{any_block_id}. Check if the response contains the consentedContent field with post content.
    Affected if The API returns content from private, draft, or unpublished posts without authentication.
  5. Inspect permission_callback configuration
    Examine the REST route registration in the plugin code at wp-content/plugins/complianz/core/rest.php (or similar) and look for 'permission_callback' => '__return_true' on the consent-area route.
    Affected if The consent-area route uses __return_true or lacks proper capability checks.

If Complianz plugin versions before 7.4.6 are installed AND the /wp-json/complianz/v1/consent-area/ endpoint responds to unauthenticated requests, the environment is affected by this IDOR vulnerability allowing unauthorized content disclosure.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 7.4.6 or later which contains proper authorization checks. Alternatively, implement a proper permission_callback function that validates user capabilities and post status before returning content.

Recommended fix Moderate confidence

Complianz – GDPR/CCPA Cookie Consent version 7.4.6 or latest available version

  1. Check the current version of the Complianz – GDPR/CCPA Cookie Consent plugin installed on the WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the Complianz plugin and note the current version number
  4. Check the WordPress plugin repository or the plugin developer's website for the latest version
  5. If the installed version is 7.4.5 or earlier, update to the latest available version (7.4.6 or later)
  6. After updating, verify the REST API endpoint behavior by attempting to access the /wp-json/complianz/v1/consent-area/ endpoint as an unauthenticated user - it should now properly enforce authorization
  7. Review the plugin settings to ensure cookie consent functionality continues to work correctly after the update
Caveat Minor: Review plugin settings after upgrade to ensure cookie consent configurations remain intact

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4019 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4019 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data