Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconIdentify site with 'Everyone' Forminator-Automator recipe
-
DeliverySubmit form with crafted serialized payload
-
ExploitTrigger PHP object injection in fr_token
-
InstallAction_Helpers_Email __destruct deletes wp-config.php
-
C2Site drops to WordPress setup state
-
ExecuteComplete install to attacker DB
-
ImpactRemote code execution
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a specific, non-default deployment: the Forminator forms plugin must be installed and at least one Forminator form must be connected to an Uncanny Automator recipe whose trigger is configured for 'Everyone', which is precisely what permits unauthenticated attackers to submit the malicious serialized payload into the fr_token deserialization path. No authentication is needed (CVSS PR:N) and no user interaction is required (UI:N). Limiting factors that reduce real-world exposure: the vulnerability is inert on sites without the Forminator integration or without an anonymous/'Everyone' recipe, the attacker must craft a valid serialized object exercising the Action_Helpers_Email __destruct() gadget (reflected in CVSS AC:H), and impact depends on the web server user having permission to delete the targeted file (e.g. wp-config.php) - the RCE step further depends on the site being reachable in its post-deletion install state. |
| Impact | Signals are moderately consistent. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.1 High) shows a network-reachable, unauthenticated flaw with full CIA impact but AC:H - the high attack complexity correctly reflects that exploitation is not universal: it depends on a specific, non-default plugin configuration (Forminator form bound to an 'Everyone' recipe) and on crafting a working serialized gadget payload. No EPSS score was provided, so probabilistic exploitation likelihood cannot be quoted, and there is no CISA KEV entry and no SSVC decision data in the input. There is no evidence of active exploitation and no public exploit was identified at time of analysis, so this is not confirmed in-the-wild activity; however, the fact that the gadget chain is self-contained within the plugin materially lowers the bar for a competent attacker versus a typical POI bug that needs an external gadget library. Net: a real priority for sites running the vulnerable configuration (unauthenticated pre-auth RCE potential), but the AC:H configuration dependency, not raw CVSS, is the true gating factor - verify whether any Forminator-to-Automator 'Everyone' recipes exist before treating it as universally critical. |
| Exploit ScenarioDerived | An attacker locates a WordPress site running Uncanny Automator ≤7.3.1.4 with a public Forminator form wired to an 'Everyone' recipe, then submits the form with a field containing a crafted serialized PHP object targeting the Action_Helpers_Email __destruct() gadget. When the object is rehydrated and destructed server-side, the plugin deletes wp-config.php, forcing WordPress into its fresh-install state that the attacker completes to point the site at an attacker-controlled database and gain code execution. No public exploit was identified at time of analysis, but the in-plugin gadget chain means no external POI library is required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 16, 2026
Arbitrary file deletion in the Uncanny Automator WordPress plugin (all versions through 7.3.1.4) lets unauthenticated attackers delete any file on the server via untrusted PHP object deserialization in the fr_token function, and deleting a critical file such as wp-config.php can pivute WordPress into an installation/setup state that yields remote code execution. Exploitation is gated by a specific setup: a Forminator form must be connected to an Uncanny Automator recipe whose trigger is configured for 'Everyone', which is what exposes the deserialization sink to anonymous form submissions. A self-contained gadget chain via Action_Helpers_Email::__destruct() ships inside the plugin, so no external gadget library is needed; reported by Wordfence with no public exploit identified at time of analysis and no CISA KEV listing.
RemediationAI
Upstream fix available (WordPress.org plugin changeset 3607776); released patched version not independently confirmed from the provided data - update the Uncanny Automator plugin to the latest version above 7.3.1.4 as published on WordPress.org and confirm the fixed version in the Wordfence advisory before relying on it. Until patched, the most targeted compensating control is to break the exploit precondition: reconfigure or disable any Uncanny Automator recipe whose Forminator trigger is set to 'Everyone' (anonymous), or temporarily deactivate the Forminator-to-Automator integration, which stops anonymous form submissions from reaching the deserialization sink at the cost of losing those automation workflows. As defense in depth, place a WAF rule to block serialized PHP object markers (e.g. 'O:' patterns) in Forminator submission fields, restrict filesystem permissions so the web user cannot delete wp-config.php or core files, and monitor for unexpected deletion of wp-config.php or entry into the WordPress setup/installation flow. Reference the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/9f2774e8-8b55-4c25-93c3-e0806208b1f3?source=cve) and the fix changeset (https://plugins.trac.wordpress.org/changeset?reponame=&old=3607776%40uncanny-automator&new=3607776%40uncanny-automator).
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-502 (Deserialization of Untrusted Data), a PHP Object Injection pattern. The Forminator integration's anonymous submit handler (anon-fr-submitform.php) and token layer (fr-tokens.php fr_token, line 136) accept a serialized payload from the form submission and pass it through PHP unserialize() without validating the resulting object graph or the file paths it references. Because the trigger data is persisted and later rehydrated (via the triggers DB handler), attacker-controlled objects are instantiated in the plugin's context. The 'gadget chain' abuses PHP's automatic __destruct() invocation: the Action_Helpers_Email email trait (trait-action-helpers-email.php, line 481) and the email attachment handler (handler.php, line 201) perform filesystem operations on object properties during cleanup, so a crafted object leads to unlink()/deletion of an attacker-chosen path. The affected component is uncannyowl's 'Uncanny Automator - Easy Automation, Integration, Webhooks & Workflow Builder Plugin' (CPE cpe:2.3:a:uncannyowl:uncanny_automator...), which depends on the separate Forminator forms plugin being installed and wired into a recipe.
Know when PHP gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Network-reachable and unauthenticated via anonymous form (AV:N/PR:N/UI:N); AC:H because a specific non-default Forminator-'Everyone' recipe and a crafted gadget payload are required; file deletion enabling RCE gives full C:H/I:H/A:H.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
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.
Executive ViewAI
Uncanny Automator WordPress plugin (versions ≤7.3.1.4) contains a critical vulnerability enabling unauthenticated arbitrary file deletion and remote code execution on affected installations. Organizations running this plugin with Forminator forms accessible to the public face immediate risk of website compromise, data loss, and operational shutdown. No vendor patches are currently available, requiring immediate interim action.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) disable or uninstall Uncanny Automator plugin until patch release; (2) restrict Forminator form access to authenticated users; (3) deploy WAF rules blocking POST submissions to form handlers; (4) implement file integrity monitoring on wp-config.php and core WordPress files; (5) enforce restrictive file permissions on WordPress installation directory; (6) maintain offline backups for recovery; (7) monitor logs for signs of exploitation or unauthorized file access.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
EUVD-2026-44889
GHSA-m5q4-xwgp-qwg2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB