Atomic Edge analysis of CVE-2026-124251: The WPIDE – File Manager & Code Editor plugin for WordPress (versions up to and including 3.6.4) is vulnerable to Cross-Site Request Forgery (CSRF) due to missing nonce validation on an unspecified function. An unauthenticated attacker can trick a site administrator into performing an unauthorized action, such as clicking a link, which executes a forged request. The CVSS score is 4.3 (Medium), and the CWE is 352 (Cross-Site Request Forgery).
The root cause lies in the plugin’s security check located in `wpide/App/Services/Security/Security.php`. The vulnerable version (3.6.4) validates the request method and nonce (via the `$config` array), but does not restrict the request’s `Content-Type` header. This allows an attacker to craft a request with a `Content-Type` such as `text/plain` or `application/x-www-form-urlencoded` that bypasses typical CSRF protections (e.g., WordPress nonce checks) because the nonce is not validated for these content types. The patch adds an `isAllowedContentType` method and a check in the security handler to reject any content type that is not `application/json`, `multipart/form-data`, or empty. This blocks HTML form submissions that can be triggered cross-site.
Exploitation requires the attacker to host a malicious HTML page containing a form that auto-submits to the vulnerable endpoint. The endpoint is any WPIDE AJAX action (e.g., `wp_ajax_wpide_*`) that is protected by the flawed security check. The attacker sets the form’s `enctype` to `text/plain` or `application/x-www-form-urlencoded`, includes the necessary parameters (e.g., `action`, file path, content), and lures a logged-in administrator to visit the page. The administrator’s browser sends the forged request with the admin’s cookies, and the plugin processes the action without validating the nonce, leading to unauthorized file operations (e.g., file upload, deletion, or code execution).
The patch in version 3.6.5 adds a `Content-Type` check in `Security.php` after the method and nonce validation. The `isAllowedContentType` function allows only `application/json`, `multipart/form-data`, and an empty content type. Any other content type (e.g., `text/plain`, `application/x-www-form-urlencoded`) returns a 415 Unsupported Media Type error and logs the event. This prevents CSRF attacks that rely on HTML form submissions, as those forms cannot send `application/json` or `multipart/form-data` without CORS preflight (which would be blocked). The patch effectively closes the CSRF vector by enforcing the expected content types for the plugin’s AJAX endpoints.
If exploited, this vulnerability allows an unauthenticated attacker to perform arbitrary file operations (upload, edit, delete) within the WordPress installation, potentially leading to remote code execution by uploading a malicious PHP file. The attacker must trick an administrator into visiting a malicious page, but once the forged request is processed, the attacker gains the same privileges as the administrator for the targeted action. This can result in full site compromise, data theft, or defacement.







