CVE-2023-34030

Complianz <= 6.4.5 (Premium <= 6.4.7) - Cross-Site Request Forgery

2023-06-20 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 6.4.8
Affected Version
<= 6.4.7
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-34030
View all Complianz Premium – GDPR/CCPA Cookie Consent vulnerabilities

At a glance

CVE-2023-34030 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Complianz Premium WordPress plugin, affecting versions <= 6.4.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.4.8; sites on affected versions should update now. Disclosed June 2023, reported by Rafie Muhammad.

Vulnerability Overview

The Complianz plugin for WordPress is vulnerable to Cross-Site Request Forgery to Stored Cross-Site Scripting in versions up to, and including, 6.4.5 (Free) and 6.4.7 (Premium). This is due to missing nonce validation on several functions called via AJAX actions such as cmplz_delete_cookiebanner(), cmplz_duplicate_cookiebanner(), maybe_install_suggested_plugins (), and ajax_create_pages() to list a few. This makes it possible for unauthenticated attackers to invoke these functions and perform multiple actions like deleting/duplicating cookie banners installing suggested plugins, creating pages, and more via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Complianz Premium <= 6.4.7 carries this weakness at cmplz_delete_cookiebanner(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Complianz Premium the fix is 6.4.8: builds <= 6.4.7 are affected, anything from 6.4.8 onward is not.

Remediation

Update to version 6.4.8, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Complianz Premium: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Complianz Premium 6.4.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C