CVE-2026-49766
Description
WP User Manager plugin <=2.9.16 allows authenticated subscribers to delete arbitrary files, leading to site compromise.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
WP User Manager plugin <=2.9.16 allows authenticated subscribers to delete arbitrary files, leading to site compromise.
Vulnerability
The WP User Manager plugin for WordPress versions 2.9.16 and earlier contains an arbitrary file deletion vulnerability that can be triggered by authenticated users with the Subscriber role [1]. The flaw resides in a file deletion function that fails to properly validate the file path, allowing an attacker to delete any file on the server.
Exploitation
An attacker needs only a valid subscriber account on a WordPress site running the vulnerable plugin. No additional privileges or user interaction beyond authentication are required. The vulnerability is actively being exploited in mass campaigns, indicating that exploitation is trivial [1]. The attacker can send a crafted request to delete arbitrary files, including critical WordPress core files.
Impact
Successful exploitation allows an attacker to delete arbitrary files from the server, which can render the website inoperable, cause data loss, or enable further attacks by removing security controls. The CVSS score of 9.9 reflects the critical nature of this vulnerability [1].
Mitigation
The vulnerability is fixed in version 2.9.17 of the WP User Manager plugin. Users are strongly advised to update immediately. Patchstack has also released a virtual mitigation rule to block attacks until the update is applied [1]. No other workarounds are available.
AI Insight generated on Jun 15, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2<=2.9.16+ 1 more
- (no CPE)range: <=2.9.16
- (no CPE)range: <=2.9.16
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
1- Wordfence Intelligence Weekly WordPress Vulnerability Report (June 1, 2026 to June 7, 2026)Wordfence Blog · Jun 11, 2026