← All security briefings

Attention

AutomatorWP privilege escalation via dynamic role data (CVE-2026-104768)

Identifiers: CVE-2026-104768

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

Wordfence reports an unauthenticated privilege escalation flaw in the AutomatorWP plugin (slug automatorwp) through version 6.0.4. When an anonymous automation assigns a user role from dynamically supplied trigger data, such as a comment author field, an attacker can influence the role given to the created account. The 6.0.5 patched release or newer carries the fix; the current vendor release is 6.0.8.

Classification reason: Checked as of 8 November 2026. The Wordfence notice published 6 November 2026 and updated 7 November 2026, together with the CVE record, lists 6.0.4 and earlier as affected and names 6.0.5 as the patched release. The vendor 6.0.5 changelog describes role assignment security across all role-modifying actions.

Impact

Under those conditions, routine administrator approval of a comment can create a privileged account using the attacker's email, with the password delivered by the standard WordPress new-user notification. The attacker then holds an administrator account and full control of the site.

Who is affected

Sites on AutomatorWP 6.0.4 or earlier that run an anonymous automation whose Role option is bound to attacker-influenced trigger data, such as a comment author field, and where an administrator approves the attacker's comment in the reviewed path. Both conditions must hold. The weakness sits in the role-assigning action, which did not cap the role that trigger data could set; it is not a flaw in every automatically created account, and not all automations are affected. Version 6.0.4 remains affected despite its changelog note about guarding dynamic admin creation.

Products and versions

Products and versionsAffectedFixed
AutomatorWP – No-Code Workflow Automation, Integration & Webhooks Plugin, now with AI <= 6.0.4 6.0.5

Exploitation evidence

Exploitation not established. The public sources do not establish exploitation in the wild; the absence of reports does not prove none occurred.

Sources: Wordfence Intelligence, Wordfence / CVE Program

Actions

  1. Confirm the plugin slug automatorwp and the installed version.
  2. Review anonymous automations, their Role options and how trigger data is bound.
  3. Back up and check compatibility, then update to the 6.0.5 patched release or newer; 6.0.8 is current.
  4. If the update must wait, pause only the affected automations in a controlled way rather than disabling all commenting or uninstalling plugins; this has business impact and is not a guaranteed fix.
  5. Review unexpected new administrators, role changes, notification emails and logs; patching does not undo an earlier compromise.
  6. Test legitimate automation flows after patching.

Unknowns

  • Which existing workflows on a given site meet the vulnerable conditions.
  • Whether unauthorized accounts were already created.

Sources

  • Wordfence Intelligence · retrieved https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/automatorwp/automatorwp-604-unauthenticated-privilege-escalation-to-insufficient-role-validation-in-anonymous-automation-role-option
  • Wordfence / CVE Program · published · updated · retrieved https://cveawg.mitre.org/api/cve/CVE-2026-104768
  • AutomatorWP / WordPress Plugin Repository · retrieved https://plugins.svn.wordpress.org/automatorwp/trunk/readme.txt

Change history

  1. — Published: Published 8 November 2026 based on the Wordfence notice of 6 November 2026, updated 7 November 2026; the vendor fix in 6.0.5 and later releases was already available.

Subscribe: RSS feed · JSON Feed · Feed format and fields