UsersWP <= 1.2.63 - Insecure Direct Object Reference to Authenticated (Editor+) Arbitrary User Avatar/Banner Reset via 'user_id' Parameter
Strategic Overview
- Status
- Patched in 1.2.64
- Affected Plugin
- UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP
- Affected Version
<= 1.2.63- CVSS
- 2.7Low
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-12102
At a glance
CVE-2026-12102 is a low-severity Authorization Bypass Through User-Controlled Key vulnerability in the UsersWP WordPress plugin, affecting versions <= 1.2.63. It carries a CVSS score of 2.7 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 1.2.64; sites on affected versions should update now. Disclosed June 2026, reported by Pasindu Dilshan (K4PXD).
Vulnerability Overview
The UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.2.63 via the 'user_id' parameter due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with editor-level access and above, to reset and permanently delete the avatar or banner image of any arbitrary user, including administrators, by clearing their avatar_thumb or banner_thumb metadata in the uwp_usermeta table.
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
UsersWP <= 1.2.63 carries this weakness at user_id, and reaching it takes an account at Editor 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 UsersWP the fix is 1.2.64: builds <= 1.2.63 are affected, anything from 1.2.64 onward is not.
Remediation
Update to version 1.2.64, 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.64 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in UsersWP – Front-end login form, User Registration, User Profile & Members Directory plugin for WP
- 9.8CVE-2024-6265: UsersWP SQL Injection
CVE-2024-6265 - 8.8CVE-2026-13492: UsersWP <= 1.2.65 Arbitrary File Deletion
CVE-2026-13492 - 6.5CVE-2025-10003: UsersWP SQL Injection
CVE-2025-10003 - 6.4CVE-2026-18501: UsersWP <= 1.2.69 Stored Cross-Site Scripting
CVE-2026-18501 - 6.4CVE-2026-5742: UsersWP <= 1.2.60 Stored Cross-Site Scripting
CVE-2026-5742 - 6.4CVE-2025-9344: UsersWP <= 1.2.42 Stored Cross-Site Scripting
CVE-2025-9344 - 6.4CVE-2024-2423: UsersWP <= 1.2.6 Stored Cross-Site Scripting
CVE-2024-2423 - 6.1UsersWP – User Registration & User Profile <= 1.2.2.28 Reflected XSS
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C