CVE-2026-39468
Description
A Contributor-level arbitrary file deletion vulnerability in Meta Box for WordPress <= 5.11.1 allows authenticated attackers to delete arbitrary files.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A Contributor-level arbitrary file deletion vulnerability in Meta Box for WordPress <= 5.11.1 allows authenticated attackers to delete arbitrary files.
Vulnerability
The Meta Box – WordPress Custom Fields Framework plugin suffers from an arbitrary file deletion vulnerability in versions 5.11.1 and earlier. The flaw arises from insufficient validation of file paths when handling contributor-level requests, allowing authenticated users with Contributor access to delete arbitrary files on the server [1].
Exploitation
An authenticated attacker with a Contributor-level account on a WordPress site running the vulnerable plugin can exploit this vulnerability. The attacker sends a crafted request specifying the path of a file to be deleted. No special privileges beyond Contributor access are required, and the attack does not require user interaction from other roles [1].
Impact
Successful exploitation allows the attacker to delete arbitrary files from the WordPress installation. If critical core, plugin, or theme files are deleted, the site may become non-functional or suffer data loss. The vulnerability could be leveraged in mass-exploit campaigns to compromise thousands of sites at once [1].
Mitigation
The vulnerability is fixed in version 5.11.2 of the plugin, released on 2026-06-15. Administrators should update immediately to version 5.11.2 or later. For those unable to update, Patchstack provides a mitigation rule to block attacks until the update is applied [1].
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
1Patches
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
0No linked articles in our index yet.