CVE-2025-12775

8.8

nazsabuz · WP Dropzone

The WP Dropzone plugin for WordPress contains an arbitrary file upload vulnerability via the ajax_upload_handle function, allowing authenticated users to achieve remote code execution.

Executive summary

The WP Dropzone plugin for WordPress contains an arbitrary file upload vulnerability in versions up to 1.1.0, which allows authenticated attackers to execute arbitrary code on the server.

Vulnerability

This vulnerability is an unrestricted file upload flaw (CWE-434) within the ajax_upload_handle function. It permits authenticated attackers with subscriber-level access or higher to upload malicious files directly to the server, potentially leading to remote code execution.

Business impact

Successful exploitation of this vulnerability allows an attacker to execute arbitrary code on the host server, leading to a complete compromise of the WordPress installation. Given the CVSS score of 8.8, this represents a high-severity risk that could result in total data loss, unauthorized access to sensitive information, and potential lateral movement within the network.

Remediation

Immediate Action: Since a specific patched version is not confirmed in the provided data, administrators should immediately deactivate and remove the WP Dropzone plugin from their WordPress environment until a secure update is released by the developer.

Proactive Monitoring: Monitor server access logs for suspicious POST requests directed at the WordPress uploads directory or unusual file extensions being created in the plugin's upload path.

Compensating Controls: Implement a Web Application Firewall (WAF) rule to block unauthorized file uploads and restrict access to the plugin's AJAX endpoints to trusted user roles only.

Exploitation status

Public Exploit Available: No (exploit_available: false)

Analyst recommendation

This vulnerability presents a significant risk to site integrity and server security. Due to the potential for remote code execution, it is imperative that organizations prioritize the removal of the vulnerable plugin. Security teams should audit their WordPress installations to identify any active instances of WP Dropzone and ensure that all plugins are kept updated or removed if they lack active vendor support.

Sources

Originally found and disclosed by Kenneth Dunn, per the CVE Program record.