CVE-2023-33333

Complianz <= 6.4.4 (Premium <= 6.4.6.1) - Cross-Site Request Forgery to Stored Cross-Site Scripting

2023-06-21 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 6.4.5
Affected Version
<= 6.4.4
CVSS
6.1Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-33333
View all Complianz – GDPR/CCPA Cookie Consent vulnerabilities

At a glance

CVE-2023-33333 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Complianz WordPress plugin, affecting versions <= 6.4.4. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.4.5; 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.4 (Free) and 6.4.6.1 (Premium). This is due to missing nonce validation on the ajax_script_add() and ajax_script_save() functions called via AJAX actions. This makes it possible for unauthenticated attackers to invoke this function and add web scripts to a site 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 <= 6.4.4 carries this weakness at ajax_script_add(), 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 the fix is 6.4.5: builds <= 6.4.4 are affected, anything from 6.4.5 onward is not.

Remediation

Update to version 6.4.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Complianz: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Complianz 6.4.5 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