CVE-2023-34005

Front End Users <= 3.2.24 - Cross-Site Request Forgery

2023-04-07 00:00
thiennv

Strategic Overview

Status
Patched in 3.2.25
Affected Plugin
Front End Users
Affected Version
<= 3.2.24
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-34005
View all Front End Users vulnerabilities

At a glance

CVE-2023-34005 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Front End Users WordPress plugin, affecting versions <= 3.2.24. 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 3.2.25; sites on affected versions should update now. Disclosed April 2023, reported by thiennv.

Vulnerability Overview

The Front End Users plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.2.24. This is due to missing or incorrect nonce validation on several functions such as Mass_Delete_EWD_FEUP_Users, Delete_All_EWD_FEUP_Users, and Mass_Delete_EWD_FEUP_Fields. This makes it possible for unauthenticated attackers to potentially delete users, 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 Front End Users <= 3.2.24 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 Front End Users the fix is 3.2.25: builds <= 3.2.24 are affected, anything from 3.2.25 onward is not.

Remediation

Update to version 3.2.25, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-34005https://www.wordfence.com/threat-intel/vulnerabilities/id/ee13399f-0fc9-40f3-93f5-34c913d54aa0https://nvd.nist.gov/vuln/detail/CVE-2023-34005

Related records

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