Front End Users <= 3.2.24 - Missing Authorization to Unauthenticated Registered User Deletion

2023-04-07 00:00
Anonymous

Strategic Overview

Status
Patched in 3.2.25
Affected Plugin
Front End Users
Affected Version
<= 3.2.24
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE pending
View all Front End Users vulnerabilities

At a glance

This record tracks a medium-severity Missing Authorization vulnerability in the Front End Users WordPress plugin, affecting versions <= 3.2.24. It carries a CVSS score of 6.5 (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.

Vulnerability Overview

The Front End Users plugin for WordPress is vulnerable to unauthorized modification and loss of data due to a missing capability check on several functions such as Mass_Delete_EWD_FEUP_Users, Delete_All_EWD_FEUP_Users, and Mass_Delete_EWD_FEUP_Fields in versions up to, and including, 3.2.24. This makes it possible for unauthenticated users to perform restricted actions such as deleting users that have registered through the plugin configuration.

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, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Front End Users <= 3.2.24 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. 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?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. 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.

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/5ccfafaf-902f-4142-90b3-9f70800eb377

Related records

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