AutomatorWP <= 2.5.8 - Cross Site Request Forgery via bulk_delete

2023-02-14 00:00
Anonymous

Strategic Overview

Status
Patched in 2.5.9
Affected Plugin
AutomatorWP – No-Code Workflow Automation, Integration & Webhooks Plugin, now with AI
Affected Version
<= 2.5.8
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all AutomatorWP – No-Code Workflow Automation, Integration & Webhooks Plugin, now with AI vulnerabilities

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the AutomatorWP WordPress plugin, affecting versions <= 2.5.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.5.9; sites on affected versions should update now. Disclosed February 2023.

Vulnerability Overview

The AutomatorWP plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.5.8. This is due to missing or incorrect nonce validation on the bulk_delete() function. This makes it possible for unauthenticated attackers to bulk delete CT objects via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

AutomatorWP <= 2.5.8 carries this weakness at bulk_delete(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For AutomatorWP the fix is 2.5.9: builds <= 2.5.8 are affected, anything from 2.5.9 onward is not.

Remediation

Update to version 2.5.9, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to AutomatorWP: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: AutomatorWP 2.5.9 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/5ebdf903-828e-4a22-953a-17d85984b576

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C