Quick answers
- Is CVE-2026-14567 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14567 being exploited in the wild.
- How severe is CVE-2026-14567?
- Medium severity, with a CVSS score of 5.3, published 28 August 2026.
- Which products and versions are affected?
- WP User Frontend WP User Frontend before 4.3.10.
- Is there a fix for CVE-2026-14567?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-14567 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-14567?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The plugin's REST API endpoint `/wp-json/wpuf/v1/user_directory/search` does not enforce authentication or authorization checks, allowing unauthenticated attackers to query and retrieve sensitive user data. The vulnerability stems from missing access controls on the user directory search functionality; attackers can omit required parameters (such as directory_id) to bypass directory publication guards and access all user records. The endpoint returns email addresses and phone numbers in the response for every registered user. No authentication credentials, cookies, or CSRF tokens are required. The issue is fixed in version 4.3.10.
Affected products
- WP User Frontend WP User Frontend before 4.3.10
Timeline
- 2026-08-26: disclosed
- 2026-08-28: advisory