dbcve.org
ComplianzWordPress extension · Really Simple Plugins

CVE-2023-33333

HIGH · 8.8 CVSS v3.1 Published 2023-11-30
Fix available
A fix is available. Upgrade to 6.4.6 / 6.4.7 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Really Simple Plugins Complianz, Really Simple Plugins Complianz Premium allows Cross-Site Scripting (XSS).This issue affects Complianz: from n/a through 6.4.4; Complianz Premium: from n/a through 6.4.6.1.

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 · moderate confidence

A CSRF vulnerability in the Complianz WordPress plugin (versions through 6.4.4 free / 6.4.6.1 premium) allows attackers to execute malicious requests on behalf of authenticated users, potentially leading to stored XSS attacks due to insufficient CSRF protections on state-changing operations.

MitigationImplement WordPress nonces and CSRF tokens on all forms and AJAX endpoints, validate origin headers, and ensure proper request validation before processing any state-changing operations.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ComplianzWordPress extension
Affected:< 6.4.6< 6.4.7

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check installed Complianz plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Complianz. The version number is displayed below the plugin name. Alternatively, check the plugin file header in wp-content/plugins/complianz-gdpr/complianz.php for 'Version:' tag.
    Affected if Installed version is below 6.4.6 (free) or below 6.4.7 (premium)
  2. Confirm plugin is active
    In WordPress admin, verify the Complianz plugin shows as 'Active' in the Plugins list. The vulnerability only affects active installations.
    Affected if Plugin is active and version is in the vulnerable range
  3. Inspect form submissions for CSRF tokens
    Use browser developer tools or a proxy (Burp/ZAP) to intercept a Complianz form submission (e.g., settings save, cookie banner configuration). Check if the request includes a WordPress nonce field (typically '_wpnonce' or similar) and that the nonce validates properly.
    Affected if Forms submit without a valid nonce or CSRF token, or token validation is missing
  4. Test AJAX endpoints for CSRF protection
    Use a tool to send a direct POST request to wp-admin/admin-ajax.php with a Complianz-related action (e.g., any 'complianz_' prefixed action) without including a nonce. Observe if the request is processed without nonce verification.
    Affected if AJAX requests execute state-changing operations without validating a nonce or origin header
  5. Review state-changing operations
    Examine Complianz settings pages that change configuration (e.g., cookie settings, privacy statement editor, region settings). Attempt to submit a request with an invalid or missing CSRF token to see if the operation succeeds.
    Affected if State-changing operations succeed without proper CSRF token validation

Your environment is affected if the Complianz plugin version is below 6.4.6 (free) or 6.4.7 (premium) AND the plugin is active with forms/AJAX endpoints missing CSRF token validation.

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
Upgrade available Upgrade to 6.4.6 / 6.4.7 or later
Fixed in 6.4.66.4.7
Interim mitigation

Implement WordPress nonces and CSRF tokens on all forms and AJAX endpoints, validate origin headers, and ensure proper request validation before processing any state-changing operations.

Recommended fix High confidence

Complianz: 6.4.6 or later; Complianz Premium: 6.4.7 or later

  1. 1. Log in to the WordPress admin dashboard where Complianz is installed
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Complianz (or Complianz Premium) plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, manually upload the updated plugin version (6.4.6 or later for Complianz free, 6.4.7 or later for Complianz Premium)
  6. 6. After updating, verify the plugin is functioning correctly by checking the dashboard

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

Fix this in Complianz Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-33333 — 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-2023-33333 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