Uncanny Automator <= 7.3.1.4 - Unauthenticated PHP Object Injection to Arbitrary File Deletion via Forminator Submitted-Field Token
The Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the fr_token function in all versions up to, and including, 7.3.1.4. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). Exploitation requires a Forminator form connected to an Uncanny Automator recipe configured for 'Everyone', allowing unauthenticated form submissions to supply the malicious serialized payload; a gadget chain is present within the plugin via the Action_Helpers_Email __destruct() method, meaning no external gadget library is required.
Quick answer
Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin 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
- *-7.3.1.4
Fixed versions
- 7.4.0
How to fix it
Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin is affected by this security issue. The safest fix is to update to the fixed version, then test the site or service again to make sure the risky path is closed.
- Find every place where Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin is installed or used.
- Update to 7.4.0 or a later vendor-supported version.
- Back up the site or service before changing production systems.
- Apply the update in staging first if possible, then deploy it to production.
- If you cannot update right away, restrict access to the affected feature and monitor logs closely.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version or configuration is no longer in the affected range.
- Retest the affected page, API, plugin, workflow, or network path.
- Check logs after the change for blocked attempts, crashes, or errors.
- Run a fresh Fixnx scan and save the report.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-15008?
Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin versions listed as affected should be reviewed: *-7.3.1.4.
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.