UsersWP <= 1.2.3.22 - Cross-Site Request Forgery

2023-11-01 00:00
Anonymous

Strategic Overview

Status
Patched in 1.2.3.23
Affected Plugin
UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP
Affected Version
< 1.2.3.23
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP vulnerabilities

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the UsersWP WordPress plugin, affecting versions < 1.2.3.23. 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 1.2.3.23; sites on affected versions should update now. Disclosed November 2023.

Vulnerability Overview

The UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to 1.2.3.23 (exclusive). This is due to missing or incorrect nonce validation on the ajax_profile_image_remove function. This makes it possible for unauthenticated attackers to delete user images via a forged request granted they can trick a site user 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 UsersWP < 1.2.3.23 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 UsersWP the fix is 1.2.3.23: builds < 1.2.3.23 are affected, anything from 1.2.3.23 onward is not.

Remediation

Update to version 1.2.3.23, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/413d3ec0-8d04-4bef-9394-f666cfed733e

Related records

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