CVE-2026-3243
Arbitrary File Deletion in Advanced Members for ACF Plugin
Publication date: 2026-04-08
Last updated on: 2026-04-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| advanced_members | acf_plugin | to 1.2.5 (inc) |
| advanced_members | acf | to 1.2.5 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should update the Advanced Members for ACF plugin to a version later than 1.2.5, as the vulnerability was partially patched in version 1.2.5.
Additionally, restrict Subscriber-level users from accessing or executing functions that could lead to arbitrary file deletion until the update is applied.
Can you explain this vulnerability to me?
The Advanced Members for ACF plugin for WordPress has a vulnerability in its create_crop function due to insufficient validation of file paths. This flaw allows authenticated users with Subscriber-level access or higher to delete arbitrary files on the server.
Because the plugin does not properly check the file paths, attackers can specify files to delete beyond what should be allowed, potentially removing critical files such as wp-config.php.
This vulnerability was partially fixed in version 1.2.5, but all versions up to and including 1.2.5 remain affected.
How can this vulnerability impact me? :
This vulnerability can have severe impacts because it allows attackers to delete arbitrary files on the server.
Deleting critical files like wp-config.php can lead to remote code execution, which means attackers could gain full control over the affected WordPress site.
Such control can result in data breaches, site defacement, loss of service, or further exploitation of the server.