HomeWordPress vulnerabilitiesUncanny Automator
Uncanny Automator vulnerabilities
Uncanny Automator has 8 known vulnerabilities in this database. The most recent published record is dated 8 Oct 2026.
- Known vulnerabilities
- 8
- Active installs
- 40,000+
- Latest version
- 7.7.0
- Last updated
- 30 Sep 2026
- Most recent
- 8 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Arbitrary file deletion CVE-2026-82627 | High 7.5 | Up to 7.6.1.1 | Fixed in a later version (latest 7.7.0) | 1 h ago |
| Broken access control CVE-2026-15025 | High 7.5 | Up to 7.3.2 | Fixed in a later version (latest 7.7.0) | 28 Jul 2026 |
| Remote code execution CVE-2026-15008 | High 8.1 | Up to 7.3.1.4 | Fixed in a later version (latest 7.7.0) | 16 Jul 2026 |
| Cross-site scripting (XSS) CVE-2025-15522 | Medium 6.4 | Up to 6.10.0.2 | Fixed in a later version (latest 7.7.0) | 23 Jan 2026 |
| PHP object injection CVE-2025-3623 | Critical 9.1 | Before 6.4.0.2 | Fixed in 6.4.0.2 | 14 May 2025 |
| Broken access control CVE-2025-4520 | Medium 5.4 | Before 6.5.0 | Fixed in 6.5.0 | 14 May 2025 |
| Privilege escalation CVE-2025-2075 | High 8.8 | Before 6.4 | Fixed in 6.4 | 4 Apr 2025 |
| Server-side request forgery (SSRF) CVE-2024-13838 | Medium 5.5 | Before 6.3 | Fixed in 6.3 | 12 Mar 2025 |
Read the published descriptions
- CVE-2026-82627, 8 Oct 2026
- The Uncanny Automator - AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 7.6.1.1 via deserialization of untrusted input. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject a PHP Object when a third-party integration plugin (such as PeepSo, MailPoet, WPForms, etc) is installed and a recipe is configured that stores attacker-controlled data as trigger meta. The additional presence of a POP chain within Uncanny Automator allows attackers to delete arbitrary files on the server. CVE record
- CVE-2026-15025, 28 Jul 2026
- The Uncanny Automator - Easy Automation, Integration, Webhooks & Workflow Builder plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 7.3.2 via the automator_google_contacts_fetch_labels, automator_mautic_segment_fetch, automator_mautic_tags_fetch, and automator_mautic_render_contact_fields AJAX actions due to a missing capability check and missing nonce verification in the corresponding handlers (ajax_fetch_labels, segments_fetch, tags_fetch, and render_contact_fields). This makes it possible for authenticated attackers, with Subscriber-level access and above, to enumerate sensitive Google Contacts groups/labels and Mautic segments, tags, and contact-field definitions retrieved via integration credentials configured by an administrator, and to consume third-party API quota. CVE record
- CVE-2026-15008, 16 Jul 2026
- 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. CVE record
- CVE-2025-15522, 23 Jan 2026
- The Uncanny Automator - Easy Automation, Integration, Webhooks & Workflow Builder Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the automator_discord_user_mapping shortcode in all versions up to, and including, 6.10.0.2 due to insufficient input sanitization and output escaping on the verified_message parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user with a verified Discord account accesses the injected page. CVE record
- CVE-2025-3623, 14 May 2025
- The Uncanny Automator plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 6.4.0.1 via deserialization of untrusted input in the automator_api_decode_message() function. This makes it possible for unauthenticated to inject a PHP Object. The additional presence of a POP chain allows attackers to delete arbitrary files. CVE record
- CVE-2025-4520, 14 May 2025
- The Uncanny Automator plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on multiple AJAX functions in versions up to, and including, 6.4.0.2. This makes it possible for authenticated attackers, with subscriber-level permissions or above to update plugin settings. CVE record
- CVE-2025-2075, 4 Apr 2025
- The Uncanny Automator - Easy Automation, Integration, Webhooks & Workflow Builder Plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 6.3.0.2. This is due to add_role() and user_role() functions missing proper capability checks performed through the validate_rest_call() function. This makes it possible for unauthenticated attackers to set the role of arbitrary users to administrator granting full access to the site, though privilege escalation requires an active account on the site so this is considered an authenticated privilege escalation. CVE record
- CVE-2024-13838, 12 Mar 2025
- The Uncanny Automator - Easy Automation, Integration, Webhooks & Workflow Builder Plugin plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 6.2 via the 'call_webhook' method of the Automator_Send_Webhook class This makes it possible for authenticated attackers, with Administrator-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. CVE record
What to do if you run Uncanny Automator
If you run Uncanny Automator, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Uncanny Automator vulnerabilities
Free. We email you when a new vulnerability is published for Uncanny Automator, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.