Descrizione
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.
Come correggere
Priorità: Media — correggere nel prossimo ciclo di patch. Motivazione: CVSS 7.5, EPSS 0.6% (percentile 47).
Versioni da aggiornare
Il record non riporta ancora i prodotti e le versioni corrette (analisi NVD in corso). Consultare l'advisory del vendor nei riferimenti.
Mitigazioni temporanee
Da applicare solo se non è possibile aggiornare subito:
- Restringere l'accesso al componente, applicare il principio del minimo privilegio e controllare i log per operazioni non autorizzate.
Verifica
- Individuare tutti gli asset con il prodotto interessato (inventario, scanner di vulnerabilità, CMDB).
- Confrontare la versione installata con quelle indicate sopra.
- Applicare l'aggiornamento in un ambiente di test, poi in produzione; riavviare i servizi se richiesto.
- Ripetere la scansione per confermare la correzione.
Riferimenti
- Riferimentohttps://plugins.trac.wordpress.org/browser/automatorwp/tags/6.0.3/includes/events.php#L1303
- Riferimentohttps://plugins.trac.wordpress.org/browser/automatorwp/tags/6.0.3/integrations/automatorwp/actions/anonymous-user.php#L487
- Riferimentohttps://plugins.trac.wordpress.org/browser/automatorwp/tags/6.0.3/integrations/automatorwp/actions/anonymous-user.php#L500
- Riferimentohttps://plugins.trac.wordpress.org/browser/automatorwp/tags/6.0.3/integrations/wordpress/actions/create-user.php#L174
- Riferimentohttps://plugins.trac.wordpress.org/browser/automatorwp/tags/6.0.3/integrations/wordpress/actions/user-role.php#L149
- Riferimentohttps://plugins.trac.wordpress.org/browser/automatorwp/tags/6.0.3/integrations/wordpress/triggers/anonymous-comment-post-type.php#L111
- Riferimentohttps://plugins.trac.wordpress.org/changeset?reponame=&old=3754573%40automatorwp&new=3754573%40automatorwp
- Riferimentohttps://www.wordfence.com/threat-intel/vulnerabilities/id/6138f184-4475-4288-835f-9bf8c21f9147?source=cve