CVE-2023-6384

WP User Profile Avatar <= 1.0.0 - Authenticated (Author+) Insecure Direct Object Reference to Avatar Deletion/Update

2023-12-29 00:00
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 1.0.1
Affected Plugin
WP User Profile Avatar
Affected Version
<= 1.0.0
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2023-6384
View all WP User Profile Avatar vulnerabilities

At a glance

CVE-2023-6384 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP User Profile Avatar WordPress plugin, affecting versions <= 1.0.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.0.1; sites on affected versions should update now. Disclosed December 2023, reported by Dmitrii Ignatyev.

Vulnerability Overview

The WP User Profile Avatar plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.0.0 via the remove_user_avatar and update_user_avatar functions due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to update and delete arbitrary avatars.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in WP User Profile Avatar <= 1.0.0 takes an account at Author level or above. 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 WP User Profile Avatar the fix is 1.0.1: builds <= 1.0.0 are affected, anything from 1.0.1 onward is not.

Remediation

Update to version 1.0.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: WP User Profile Avatar 1.0.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-2023-6384https://www.wordfence.com/threat-intel/vulnerabilities/id/75c325a1-1a88-4b67-a5f8-6307627d8c6ahttps://nvd.nist.gov/vuln/detail/CVE-2023-6384

Related records

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