CVE-2022-0442

UsersWP <= 1.2.3 - Subscriber+ User Avatar Override

2022-02-14 00:00
Felipe de Avila

Strategic Overview

Status
Patched in 1.2.3.1
Affected Plugin
UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP
Affected Version
< 1.2.3.1
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2022-0442
View all UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP vulnerabilities

At a glance

CVE-2022-0442 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the UsersWP WordPress plugin, affecting versions < 1.2.3.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 1.2.3.1; sites on affected versions should update now. Disclosed February 2022, reported by Felipe de Avila.

Vulnerability Overview

The UsersWP WordPress plugin before 1.2.3.1 is missing access controls when updating a user avatar, and does not make sure file names for user avatars are unique, allowing a logged in user to overwrite another users avatar.

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

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in UsersWP < 1.2.3.1 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For UsersWP the fix is 1.2.3.1: builds < 1.2.3.1 are affected, anything from 1.2.3.1 onward is not.

Remediation

Update to version 1.2.3.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: UsersWP 1.2.3.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-0442https://www.wordfence.com/threat-intel/vulnerabilities/id/f31b42c8-cf82-49cf-ac4c-d42a28252d66https://nvd.nist.gov/vuln/detail/CVE-2022-0442

Related records

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