CVE-2025-12733

WordPress · WordPress plugin: Import any XML, CSV or Excel File to WordPress (WP All Import)

A high-severity vulnerability has been identified in the "WP All Import" plugin for WordPress, which allows for remote code execution.

Executive summary

A high-severity vulnerability has been identified in the "WP All Import" plugin for WordPress, which allows for remote code execution. An attacker could exploit this flaw to gain complete control over an affected website, potentially leading to data theft, website defacement, or the installation of malware. Due to the critical nature of this vulnerability, immediate action is required to prevent a compromise.

Vulnerability

The vulnerability allows a remote attacker to execute arbitrary code on the server hosting the WordPress site. This is possible due to insufficient input validation and sanitization when the plugin processes imported files (XML, CSV, or Excel). An attacker can craft a malicious file containing executable code (e.g., PHP) and upload it through the plugin's import functionality. When the plugin parses this file, the embedded code is executed with the privileges of the web server's user account, leading to a full server compromise.

Business impact

This vulnerability is rated as High severity with a CVSS score of 8.8. Successful exploitation could have a catastrophic impact on the business. An attacker could gain complete control of the web server, enabling them to steal sensitive information such as customer data, personally identifiable information (PII), and payment details. Further risks include significant reputational damage from a public breach or website defacement, financial losses from regulatory fines (e.g., GDPR, CCPA) and remediation costs, and operational disruption. The compromised server could also be used as a pivot point to launch further attacks against the internal network.

Remediation

Immediate Action:

  • Update: Immediately update the "Import any XML, CSV or Excel File to WordPress (WP All Import)" plugin to the latest patched version provided by the vendor.
  • Review and Remove: If the plugin is not critical for business operations, the recommended course of action is to disable and uninstall it to completely eliminate the attack surface.
  • Verify: After updating or removing the plugin, verify that the changes have been successfully applied and the site is functioning correctly.

Proactive Monitoring:

  • Log Analysis: Monitor web server access logs for unusual POST requests to the plugin's file upload endpoints. Scrutinize logs for evidence of suspicious file names or types being uploaded.
  • File Integrity Monitoring (FIM): Use FIM tools to monitor for unauthorized changes to core WordPress files, plugin directories, or the creation of unexpected files (e.g., .php, .sh) in web-accessible locations.
  • Network Traffic: Monitor for anomalous outbound network connections from the web server, which could indicate a command-and-control (C2) channel established by an attacker post-exploitation.

Compensating Controls:

  • Web Application Firewall (WAF): Implement and configure a WAF to block malicious file uploads and common patterns associated with remote code execution attempts.
  • Principle of Least Privilege: Ensure the web server process runs with the minimum permissions necessary, limiting an attacker's ability to escalate privileges or access sensitive system files if a compromise occurs.
  • Disable Unnecessary PHP Functions: Harden the server's PHP configuration by disabling dangerous functions (e.g., exec(), shell_exec(), system()) if they are not required by legitimate applications.

Exploitation status

Public Exploit Available: False

Analyst recommendation

Given the high severity (CVSS 8.8) of this Remote Code Execution vulnerability, we strongly recommend that organizations treat this as a critical priority. All instances of the "WP All Import" plugin must be updated to a patched version or removed immediately. Although this CVE is not yet on the CISA KEV list, its potential for widespread and severe impact warrants an emergency patching cycle. Following remediation, a thorough review for indicators of compromise is advised to ensure the vulnerability has not already been exploited.