Code Engine <= 0.3.5 - Authenticated (Contributor+) Remote Code Execution
The Code Engine plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 0.3.5 via the 'code-engine' shortcode. This is due to the plugin not restricting access to the code injecting functionality of the plugin. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server.
Quick answer
Code Engine – PHP Snippets, AI Functions & Automation for WordPress should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-0.3.5
Fixed versions
- 0.3.6
How to fix it
Code Engine – PHP Snippets, AI Functions & Automation for WordPress is affected by CVE-2025-6784, a WordPress plugin vulnerability issue in versions up to 0.3.5. Wordfence lists the official remediation as updating to version 0.3.6, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, support, booking, import/export, page-builder, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or feature, restrict access, and monitor for exploitation until the update is installed.
- Inventory every WordPress site that has Code Engine – PHP Snippets, AI Functions & Automation for WordPress installed, including production, staging, multisite, client, WooCommerce, support, booking, and content-management environments.
- Confirm the installed Code Engine – PHP Snippets, AI Functions & Automation for WordPress version and compare it with the affected range from the Wordfence advisory.
- Update Code Engine – PHP Snippets, AI Functions & Automation for WordPress to version 0.3.6, or to a newer vendor-supported patched version from the official WordPress update channel.
- If the update cannot be applied immediately, disable Code Engine – PHP Snippets, AI Functions & Automation for WordPress or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
- Review plugin data, recent administrative actions, logs, and affected workflows for suspicious changes or abuse attempts.
- Rotate administrator sessions, API keys, webhook secrets, payment or integration tokens, and affected credentials if logs or content review suggest compromise.
- Clear WordPress, object, CDN, page-builder, security plugin, WooCommerce, booking/support plugin, and browser caches after patching so vulnerable assets or stored payloads are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the running Code Engine – PHP Snippets, AI Functions & Automation for WordPress version is version 0.3.6 or newer, and record the patched version in the remediation ticket.
- Verify the vulnerable workflow no longer reproduces after the update or mitigation.
- Review web server, WordPress, security plugin, WAF, database, WooCommerce, booking/support, and application logs for exploitation attempts before and after the fix.
- Retest normal visitor, subscriber, customer, editor, administrator, checkout, form, API, booking, support ticket, import/export, backup/restore, snippet, or integration workflows to confirm expected behavior still works.
- Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.
Related categories
Trusted references
FAQ
What is affected by CVE-2025-6784?
Code Engine – PHP Snippets, AI Functions & Automation for WordPress versions listed as affected should be reviewed: *-0.3.5.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.