CVE-2023-52128

White Label <= 2.9.0 - Cross-Site Request Forgery via white_label_reset_wl_admins

Strategic Overview

Status
Patched in 2.9.1
Affected Version
<= 2.9.0
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-52128
View all White Label – WordPress Custom Admin, Custom Login Page, and Custom Dashboard vulnerabilities

At a glance

CVE-2023-52128 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the White Label WordPress plugin, affecting versions <= 2.9.0. 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 2.9.1; sites on affected versions should update now. Disclosed December 2023, reported by Brandon James Roldan (tomorrowisnew).

Vulnerability Overview

The White Label plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.9.0. This is due to missing or incorrect nonce validation on the white_label_reset_wl_admins function. This makes it possible for unauthenticated attackers to reset plugin settings 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)

Reaching this weakness in White Label <= 2.9.0 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 White Label the fix is 2.9.1: builds <= 2.9.0 are affected, anything from 2.9.1 onward is not.

Remediation

Update to version 2.9.1, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

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