Uncanny Automator Easy Automation Integration Webhooks Workflow Builder Plugin
Monthly
Information disclosure in the Uncanny Automator WordPress plugin up to version 7.3.2 allows authenticated subscribers to enumerate Google Contact labels and Mautic segments, tags, and contact fields via missing capability checks and nonce verification in AJAX handlers. This enables low-privileged users to access data retrieved through administrator-configured integration credentials and potentially exhaust third‑party API quotas. No public exploit or active exploitation is known at this time.
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.
Information disclosure in the Uncanny Automator WordPress plugin up to version 7.3.2 allows authenticated subscribers to enumerate Google Contact labels and Mautic segments, tags, and contact fields via missing capability checks and nonce verification in AJAX handlers. This enables low-privileged users to access data retrieved through administrator-configured integration credentials and potentially exhaust third‑party API quotas. No public exploit or active exploitation is known at this time.
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.