CVE-2025-12733: CWE-94 Improper Control of Generation of Code ('Code Injection') in wpallimport Import any XML, CSV or Excel File to WordPress
The Import any XML, CSV or Excel File to WordPress (WP All Import) plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 3.9.6. This is due to the use of eval() on unsanitized user-supplied input in the pmxi_if function within helpers/functions.php. This makes it possible for authenticated attackers, with import capabilities (typically administrators), to inject and execute arbitrary PHP code on the server via crafted import templates. This can lead to remote code execution.
AI Analysis
Technical Summary
CVE-2025-12733 is a critical vulnerability affecting the WP All Import plugin for WordPress, specifically versions up to and including 3.9.6. The vulnerability is classified under CWE-94, indicating improper control of code generation, commonly known as code injection. The root cause is the use of PHP's eval() function on unsanitized user input within the pmxi_if function located in helpers/functions.php. This function processes import templates that can contain XML, CSV, or Excel data. Authenticated users with import capabilities—typically administrators—can craft malicious import templates that include arbitrary PHP code. When these templates are processed, the eval() function executes the injected code on the server, leading to remote code execution (RCE). The CVSS 3.1 base score is 8.8, reflecting high severity due to network attack vector (AV:N), low attack complexity (AC:L), requiring privileges (PR:L), no user interaction (UI:N), unchanged scope (S:U), and high impacts on confidentiality, integrity, and availability (C:H/I:H/A:H). Although no exploits are currently known in the wild, the vulnerability poses a significant risk because it allows attackers to fully compromise the affected WordPress server, potentially leading to data theft, site defacement, malware deployment, or pivoting to internal networks. The vulnerability affects all versions of the plugin up to 3.9.6, and no official patches or updates are listed yet, emphasizing the need for immediate mitigation.
Potential Impact
For European organizations, this vulnerability can have severe consequences. WordPress is widely used across Europe for corporate websites, e-commerce platforms, and content management systems. An attacker exploiting this vulnerability could gain full control over the web server, leading to data breaches involving personal data protected under GDPR, disruption of business operations through defacement or denial of service, and potential lateral movement into internal networks. The high integrity and availability impacts mean that attackers could alter website content, inject malicious scripts to target visitors, or render services unavailable. This is particularly critical for sectors such as finance, healthcare, media, and government agencies, where website trustworthiness and uptime are essential. The requirement for authenticated access limits exposure but does not eliminate risk, as compromised or malicious insiders could exploit this flaw. Additionally, supply chain attacks could leverage this vulnerability to compromise multiple organizations using the plugin. The absence of known exploits in the wild provides a window for proactive defense, but the high severity demands urgent attention.
Mitigation Recommendations
1. Immediately restrict import permissions to trusted administrators only, and review all user roles with import capabilities. 2. Disable or uninstall the WP All Import plugin if it is not essential to business operations until a patch is available. 3. Monitor WordPress logs and import activity for unusual or unauthorized import templates or code execution attempts. 4. Implement Web Application Firewall (WAF) rules to detect and block suspicious payloads targeting import functionality, especially those containing PHP code patterns. 5. Employ strict input validation and sanitization on import templates if custom modifications are possible. 6. Regularly update WordPress core and plugins, and subscribe to vendor security advisories for timely patch releases. 7. Conduct internal audits of WordPress user accounts to ensure no unauthorized users have import privileges. 8. Consider isolating WordPress instances in segmented network zones to limit lateral movement in case of compromise. 9. Prepare incident response plans specifically addressing web server compromises and code injection attacks. 10. Once available, apply official patches from the WP All Import plugin vendor without delay.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain, Poland, Sweden, Belgium, Ireland
CVE-2025-12733: CWE-94 Improper Control of Generation of Code ('Code Injection') in wpallimport Import any XML, CSV or Excel File to WordPress
Description
The Import any XML, CSV or Excel File to WordPress (WP All Import) plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 3.9.6. This is due to the use of eval() on unsanitized user-supplied input in the pmxi_if function within helpers/functions.php. This makes it possible for authenticated attackers, with import capabilities (typically administrators), to inject and execute arbitrary PHP code on the server via crafted import templates. This can lead to remote code execution.
AI-Powered Analysis
Technical Analysis
CVE-2025-12733 is a critical vulnerability affecting the WP All Import plugin for WordPress, specifically versions up to and including 3.9.6. The vulnerability is classified under CWE-94, indicating improper control of code generation, commonly known as code injection. The root cause is the use of PHP's eval() function on unsanitized user input within the pmxi_if function located in helpers/functions.php. This function processes import templates that can contain XML, CSV, or Excel data. Authenticated users with import capabilities—typically administrators—can craft malicious import templates that include arbitrary PHP code. When these templates are processed, the eval() function executes the injected code on the server, leading to remote code execution (RCE). The CVSS 3.1 base score is 8.8, reflecting high severity due to network attack vector (AV:N), low attack complexity (AC:L), requiring privileges (PR:L), no user interaction (UI:N), unchanged scope (S:U), and high impacts on confidentiality, integrity, and availability (C:H/I:H/A:H). Although no exploits are currently known in the wild, the vulnerability poses a significant risk because it allows attackers to fully compromise the affected WordPress server, potentially leading to data theft, site defacement, malware deployment, or pivoting to internal networks. The vulnerability affects all versions of the plugin up to 3.9.6, and no official patches or updates are listed yet, emphasizing the need for immediate mitigation.
Potential Impact
For European organizations, this vulnerability can have severe consequences. WordPress is widely used across Europe for corporate websites, e-commerce platforms, and content management systems. An attacker exploiting this vulnerability could gain full control over the web server, leading to data breaches involving personal data protected under GDPR, disruption of business operations through defacement or denial of service, and potential lateral movement into internal networks. The high integrity and availability impacts mean that attackers could alter website content, inject malicious scripts to target visitors, or render services unavailable. This is particularly critical for sectors such as finance, healthcare, media, and government agencies, where website trustworthiness and uptime are essential. The requirement for authenticated access limits exposure but does not eliminate risk, as compromised or malicious insiders could exploit this flaw. Additionally, supply chain attacks could leverage this vulnerability to compromise multiple organizations using the plugin. The absence of known exploits in the wild provides a window for proactive defense, but the high severity demands urgent attention.
Mitigation Recommendations
1. Immediately restrict import permissions to trusted administrators only, and review all user roles with import capabilities. 2. Disable or uninstall the WP All Import plugin if it is not essential to business operations until a patch is available. 3. Monitor WordPress logs and import activity for unusual or unauthorized import templates or code execution attempts. 4. Implement Web Application Firewall (WAF) rules to detect and block suspicious payloads targeting import functionality, especially those containing PHP code patterns. 5. Employ strict input validation and sanitization on import templates if custom modifications are possible. 6. Regularly update WordPress core and plugins, and subscribe to vendor security advisories for timely patch releases. 7. Conduct internal audits of WordPress user accounts to ensure no unauthorized users have import privileges. 8. Consider isolating WordPress instances in segmented network zones to limit lateral movement in case of compromise. 9. Prepare incident response plans specifically addressing web server compromises and code injection attacks. 10. Once available, apply official patches from the WP All Import plugin vendor without delay.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-11-04T22:13:08.724Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 691553e024a15f0eafbbc0a5
Added to database: 11/13/2025, 3:43:28 AM
Last enriched: 11/20/2025, 4:49:00 AM
Last updated: 12/28/2025, 2:49:23 PM
Views: 91
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-15140: SQL Injection in saiftheboss7 onlinemcqexam
MediumCVE-2025-15139: Command Injection in TRENDnet TEW-822DRE
MediumCVE-2025-15138: Path Traversal in prasathmani TinyFileManager
MediumCVE-2025-15137: Command Injection in TRENDnet TEW-800MB
HighCVE-2025-15136: Command Injection in TRENDnet TEW-800MB
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.