Skip to main content
← Vulnerabilities

AutomatorWP <= 6.0.4 - Unauthenticated Privilege Escalation to Insufficient Role Validation in Anonymous Automation 'Role' Option

7.5HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported
Published
Last modified
21/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

Affected software is the AutomatorWP WordPress plugin (version 6.0.4 and earlier), which contains a flaw in how it validates roles for anonymous automations. An attacker can reach it remotely without logging in, but it only works if a site administrator approves a comment, and the attacker can then use it to create an administrator account and gain full control of the site.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

The AutomatorWP – No-Code Workflow Automation, Integration & Webhooks Plugin, now with AI plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 6.0.4. This is due to missing privilege-ceiling validation in the create_user() function within the anonymous-user action (and equally in the Create User and Add/Change Role WordPress-integration actions), which verify only that the submitted role exists via automatorwp_get_editable_roles() without confirming the role falls at or below the acting context's privilege level — allowing attacker-controlled trigger tag data (e.g., a {comment_author} tag bound to the Role option) to supply any role, including administrator, unchallenged. This makes it possible for unauthenticated attackers to create a new administrator-role account tied to an attacker-controlled email address, receiving the generated password via WordPress's new-user notification email and thereby gaining full administrative access to the site. Exploitation requires the site to have an anonymous automation configured with the Role option bound to a dynamic trigger tag such as {comment_author}, and is triggered when a site administrator performs the routine action of approving a comment — an action that provides no in-UI indication that it will mint a new privileged account from the comment author field.

cve.now Index

21Pcve.now Index 21 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.5/10CVSS 7.5, total technical impact per CISA
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 76 if added to CISA KEV
  • Would score about 71 if CISA's SSVC rates exploitation active
  • Would score about 36 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now1 day
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • rubengc AutomatorWP – No-Code Workflow Automation, Integration & Webhooks Plugin, now with AI

    through 6.0.4

Evidence 8

  1. Link
  2. Link
  3. Link
  4. Link
  5. Link
Show all 8 sourcesShow fewer sources
  1. Link
  2. Link
  3. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-104768

Is CVE-2026-104768 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-104768?

AutomatorWP – No-Code Workflow Automation, Integration & Webhooks Plugin, now with AI: through 6.0.4.Source: cve.now feed data