CVE-2026-116846

The WordPress WP User Manager plugin through 2.9.25 contains a Missing Authorization vulnerability that allows manipulating user state. This may allow unauthorized users to change the state of other users' accounts.

The WP User Manager plugin versions up to 2.9.16 contain a vulnerability that allows subscribers to delete arbitrary files.

The WordPress plugin WP User Manager (up to version 2.9.24) contains a missing authorization vulnerability that allows exploitation of incorrectly configured access control security levels. This may permit unauthorized access to user management functions.

Missing authorization in the WP User Manager plugin. Incorrectly configured access control security levels can be exploited by unauthorized users.

The WP User Manager plugin for WordPress up to version 2.9.20 contains an Improper Access Control vulnerability that allows Privilege Abuse. This results from incorrect access control.

Broken Access Control vulnerability in the WP User Manager plugin in versions up to and including 2.9.19. The vulnerability can be exploited by an unauthenticated attacker.

The WP User Manager plugin for WordPress in versions up to and including 2.9.18 is vulnerable to unauthorized modification of data due to a missing capability check on the Connect::complete() function. The function is registered on the admin_init hook and performs no current_user_can() or nonce verification before fetching Stripe credentials and writing them into the wpum_settings option. An authenticated attacker with Subscriber-level access or higher can hijack the site's Stripe integration, routing all payments to their own Stripe account.

The WP User Manager – User Profile Builder & Membership plugin for WordPress up to version 2.9.17 has a Local File Inclusion vulnerability in the profile template scope function. Unauthenticated attackers can include and execute arbitrary .php files on the server, allowing access control bypass, sensitive data disclosure, or code execution.

The WP User Manager plugin for WordPress is vulnerable to Arbitrary File Deletion in all versions up to, and including, 2.9.12. This is due to insufficient validation of user-supplied file paths in the profile update functionality combined with improper handling of array inputs by PHP's filter_input() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files on the server via the 'current_user_avatar' parameter in a two-stage attack which can make remote code execution possible.