CVE-2025-14166: CWE-94 Improper Control of Generation of Code ('Code Injection') in ludwigyou WPMasterToolKit (WPMTK) – All in one plugin
The WPMasterToolKit plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 2.13.0. This is due to the plugin allowing Author-level users to create and execute arbitrary PHP code through the Code Snippets feature without proper capability checks. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute arbitrary PHP code on the server, leading to remote code execution, privilege escalation, and complete site compromise.
AI Analysis
Technical Summary
CVE-2025-14166 is a critical vulnerability classified under CWE-94 (Improper Control of Generation of Code) affecting the WPMasterToolKit (WPMTK) WordPress plugin, versions up to and including 2.13.0. The flaw arises because the plugin's Code Snippets feature allows users with Author-level permissions or higher to create and execute arbitrary PHP code without proper capability checks. This improper validation enables authenticated attackers with Contributor-level access or above to inject and run malicious PHP code on the server hosting the WordPress site. The exploitation vector is remote and does not require additional user interaction, making it a significant risk. Successful exploitation can lead to remote code execution (RCE), privilege escalation to higher WordPress roles or even system-level access, and complete site takeover. The vulnerability affects all versions of the plugin up to 2.13.0, and no official patches or updates have been linked yet. Although the CVSS v3.1 base score is 5.3 (medium severity), the real-world impact can be much higher depending on the attacker's goals and the site's configuration. No known exploits have been reported in the wild so far, but the vulnerability's nature makes it a prime target for attackers once weaponized. The plugin is widely used in WordPress environments, which are popular globally, increasing the potential attack surface.
Potential Impact
The impact of CVE-2025-14166 is substantial for organizations running WordPress sites with the WPMasterToolKit plugin installed. An attacker with Contributor-level access, which is a relatively low privilege level, can execute arbitrary PHP code, leading to remote code execution on the web server. This can result in full site compromise, including defacement, data theft, insertion of backdoors, or pivoting to internal networks. Privilege escalation can allow attackers to gain administrative control over the WordPress site, further increasing the risk of persistent compromise. For e-commerce, government, or enterprise websites, this can lead to significant reputational damage, data breaches, and operational disruption. Since WordPress powers a large portion of the web, the vulnerability has a broad potential impact. The lack of required user interaction and the ability to exploit remotely increase the likelihood of exploitation. Organizations that allow Contributor or higher roles to users, especially in multi-user environments, are at higher risk. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate it, as attackers may develop exploits rapidly.
Mitigation Recommendations
To mitigate CVE-2025-14166, organizations should immediately restrict user roles to the minimum necessary privileges, removing Contributor or higher roles from untrusted users. Disable or restrict access to the Code Snippets feature within the WPMasterToolKit plugin until a patch is available. Monitor user activity logs for suspicious code snippet creation or execution attempts. Implement web application firewalls (WAFs) with custom rules to detect and block attempts to inject PHP code via plugin interfaces. Regularly audit installed plugins and remove or replace those that are no longer maintained or have known vulnerabilities. Encourage the plugin vendor to release a security patch and apply it promptly once available. Additionally, consider isolating WordPress installations in containerized or sandboxed environments to limit the impact of potential code execution. Backup WordPress sites regularly and verify backup integrity to enable recovery in case of compromise. Employ principle of least privilege for all WordPress users and enforce strong authentication mechanisms.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, India, Brazil, Japan, Netherlands, Italy, Spain
CVE-2025-14166: CWE-94 Improper Control of Generation of Code ('Code Injection') in ludwigyou WPMasterToolKit (WPMTK) – All in one plugin
Description
The WPMasterToolKit plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 2.13.0. This is due to the plugin allowing Author-level users to create and execute arbitrary PHP code through the Code Snippets feature without proper capability checks. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute arbitrary PHP code on the server, leading to remote code execution, privilege escalation, and complete site compromise.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-14166 is a critical vulnerability classified under CWE-94 (Improper Control of Generation of Code) affecting the WPMasterToolKit (WPMTK) WordPress plugin, versions up to and including 2.13.0. The flaw arises because the plugin's Code Snippets feature allows users with Author-level permissions or higher to create and execute arbitrary PHP code without proper capability checks. This improper validation enables authenticated attackers with Contributor-level access or above to inject and run malicious PHP code on the server hosting the WordPress site. The exploitation vector is remote and does not require additional user interaction, making it a significant risk. Successful exploitation can lead to remote code execution (RCE), privilege escalation to higher WordPress roles or even system-level access, and complete site takeover. The vulnerability affects all versions of the plugin up to 2.13.0, and no official patches or updates have been linked yet. Although the CVSS v3.1 base score is 5.3 (medium severity), the real-world impact can be much higher depending on the attacker's goals and the site's configuration. No known exploits have been reported in the wild so far, but the vulnerability's nature makes it a prime target for attackers once weaponized. The plugin is widely used in WordPress environments, which are popular globally, increasing the potential attack surface.
Potential Impact
The impact of CVE-2025-14166 is substantial for organizations running WordPress sites with the WPMasterToolKit plugin installed. An attacker with Contributor-level access, which is a relatively low privilege level, can execute arbitrary PHP code, leading to remote code execution on the web server. This can result in full site compromise, including defacement, data theft, insertion of backdoors, or pivoting to internal networks. Privilege escalation can allow attackers to gain administrative control over the WordPress site, further increasing the risk of persistent compromise. For e-commerce, government, or enterprise websites, this can lead to significant reputational damage, data breaches, and operational disruption. Since WordPress powers a large portion of the web, the vulnerability has a broad potential impact. The lack of required user interaction and the ability to exploit remotely increase the likelihood of exploitation. Organizations that allow Contributor or higher roles to users, especially in multi-user environments, are at higher risk. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate it, as attackers may develop exploits rapidly.
Mitigation Recommendations
To mitigate CVE-2025-14166, organizations should immediately restrict user roles to the minimum necessary privileges, removing Contributor or higher roles from untrusted users. Disable or restrict access to the Code Snippets feature within the WPMasterToolKit plugin until a patch is available. Monitor user activity logs for suspicious code snippet creation or execution attempts. Implement web application firewalls (WAFs) with custom rules to detect and block attempts to inject PHP code via plugin interfaces. Regularly audit installed plugins and remove or replace those that are no longer maintained or have known vulnerabilities. Encourage the plugin vendor to release a security patch and apply it promptly once available. Additionally, consider isolating WordPress installations in containerized or sandboxed environments to limit the impact of potential code execution. Backup WordPress sites regularly and verify backup integrity to enable recovery in case of compromise. Employ principle of least privilege for all WordPress users and enforce strong authentication mechanisms.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-12-05T21:21:47.576Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 693b918b650da22753edbe40
Added to database: 12/12/2025, 3:52:43 AM
Last enriched: 2/27/2026, 10:59:54 AM
Last updated: 3/24/2026, 8:39:45 PM
Views: 59
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.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.