dbcve.org
ComplianzWordPress extension · Really Simple Plugins

CVE-2023-34030

HIGH · 8.8 CVSS v3.1 Published 2023-11-30
Fix available
A fix is available. Upgrade to 6.4.8 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 Request Forgery.This issue affects Complianz: from n/a through 6.4.5; Complianz Premium: from n/a through 6.4.7.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Complianz WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions (e.g., changing settings, modifying configurations) by leveraging the browser's automatic session cookie transmission.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing forms and validate Referer/Origin headers; also set SameSite attribute on authentication cookies.

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.8

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. Confirm Complianz plugin installation
    Locate the Complianz plugin in your WordPress installation (typically in /wp-content/plugins/complianz-gdpr/) and read the main plugin file (e.g., complianz-gdpr.php) to find the version number defined in the plugin header comment
    Affected if Complianz plugin is installed and the version is less than 6.4.8
  2. Check installed version against vulnerability range
    Compare the version found in the plugin header to the affected range: any version below 6.4.8 is vulnerable
    Affected if The installed version is lower than 6.4.8 (e.g., 6.4.7, 6.4.0, 6.3.0, etc.)
  3. Verify plugin handles admin functionality
    Examine the plugin directory for admin-facing PHP files that contain form handlers, settings pages, or configuration update functions (often in /includes/ or /admin/ subdirectories)
    Affected if The plugin contains admin settings forms or configuration handlers that could process state-changing requests
  4. Confirm plugin is active with authenticated admin access
    In WordPress admin dashboard, verify Complianz is both installed and activated; CSRF attacks require an authenticated administrator session to succeed
    Affected if The plugin is active and administrators can be logged in to the WordPress site

Your environment is affected if the Complianz plugin version is below 6.4.8 and the plugin is active with admin authentication enabled, as CSRF attacks target authenticated admin sessions.

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.8 or later
Fixed in 6.4.8
Interim mitigation

Implement anti-CSRF tokens (nonces) on all state-changing forms and validate Referer/Origin headers; also set SameSite attribute on authentication cookies.

Recommended fix High confidence

Complianz 6.4.8 or later (both free and Premium versions)

  1. Update the Complianz plugin to version 6.4.8 or later via the WordPress plugin repository, dashboard, or wp-cli command: wp plugin update complianz
  2. Verify the update was successful by checking the plugin version in WP Admin > Plugins > Complianz
  3. If using Complianz Premium, ensure both Complianz and Complianz Premium are updated to 6.4.8 or later

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

Fix this in Complianz Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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