WP User Manager – User Profile Builder & Membership Plugin Vulnerability (CVE-2026-9290)

On this page

Security Alert Summary

The WP User Manager – User Profile Builder & Membership plugin for WordPress contains a Local File Inclusion (LFI) vulnerability in the profile template scope function in all versions up to and including 2.9.17. An unauthenticated attacker can include and execute arbitrary .php files on the server, which may allow access to sensitive data or execution of PHP code when .php uploads can be included.


CVE Details

  • CVE ID: CVE-2026-9290
  • Affected component: WP User Manager – User Profile Builder & Membership plugin for WordPress
  • Affected versions: All versions up to and including 2.9.17
  • Published: June 6, 2026 12:16 AM UTC
  • Last modified: June 6, 2026 12:16 AM UTC
  • CVSS v3.1: Base score 7.5, Severity HIGH, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • Authentication / privileges / user interaction: No authentication required (unauthenticated), Privileges Required: None, User Interaction: None
  • Primary impact: Confidentiality: High; Integrity: None; Availability: None
  • CWE / weakness: CWE-22 (Path Traversal)

Technical Details

This vulnerability is a Local File Inclusion (LFI) in the plugin’s profile template scope function. The flaw allows an attacker to control a file include path used by template loading logic, permitting inclusion of arbitrary .php files from the server. When included, those PHP files are executed in the context of the web server, which can lead to disclosure of sensitive files or execution of arbitrary PHP code if an attacker can upload or place a .php file on the server.

The issue is tied to the plugin’s template and routing code paths referenced in the plugin codebase (for example, includes/functions.php, templates/profile.php, and the vendor template loader and router components cited in the plugin repository). The CVE description identifies the problem as occurring via the profile template scope function; avoid exposing or relying on unvalidated file path inputs in template resolution.

Impact is limited to what an attacker can access or include on the server. The vulnerability itself does not automatically escalate WordPress user privileges, but it can be used to bypass access controls or execute PHP code when server-side storage or uploads of .php files are possible.


How This Could Impact Your Website

Consider a typical site with a site owner, several staff editors, and an external contractor or contributor who uploads files or manages content. An unauthenticated attacker exploiting this LFI could include an uploaded .php file or an existing file on the web server. Practical consequences include exposure of internal files and user data stored on the server, such as user email addresses or other sensitive configuration files, and the potential to run PHP code if a .php file can be placed on the server.

For example, an attacker might use the vulnerability to read configuration files containing database credentials or to execute a PHP file they managed to upload via another vector. This increases the risk of targeted phishing against staff or contractors if email addresses or other contact details are disclosed.

If you’re unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review.


Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, especially accounts with contributor or upload privileges.
  • Enforce strong passwords and enable two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins and themes from the site.
  • Restrict upload file types and block server execution of uploaded files where possible.
  • Monitor site activity and logs for unusual file uploads or include attempts.

If you’d like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.


References