Uncanny Automator <= 4.14 - Cross-Site Request Forgery via update_automator_connect

2023-05-24 00:00
Anonymous

Strategic Overview

Status
Patched in 4.15
Affected Plugin
Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included
Affected Version
< 4.15
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included vulnerabilities

At a glance

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

Vulnerability Overview

The Uncanny Automator plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.14. This is due to missing or incorrect nonce validation on the update_automator_connect function. This makes it possible for unauthenticated attackers to perform certain tasks in the setup wizard 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)

Reaching this weakness in Uncanny Automator < 4.15 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 Uncanny Automator the fix is 4.15: builds < 4.15 are affected, anything from 4.15 onward is not.

Remediation

Update to version 4.15, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/bd0d8661-4725-41dd-88ce-8e94e285d5b8

Related records

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