CVE-2024-13838

Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin <= 6.2 - Authenticated (Admin+) Server-Side Request Forgery via Webhook

2025-03-11 00:00
Francesco Carlucci

Strategic Overview

Status
Patched in 6.3
Affected Plugin
Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included
Affected Version
<= 6.2
CVSS
5.5Medium
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2024-13838
View all Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included vulnerabilities

At a glance

CVE-2024-13838 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the Uncanny Automator WordPress plugin, affecting versions <= 6.2. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 6.3; sites on affected versions should update now. Disclosed March 2025, reported by Francesco Carlucci.

Vulnerability Overview

The Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 6.2 via the 'call_webhook' method of the Automator_Send_Webhook class This makes it possible for authenticated attackers, with Administrator-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

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 interaction from a victim user.

CWE-918: Server-Side Request Forgery (SSRF)

Uncanny Automator <= 6.2 carries this weakness at call_webhook, and reaching it takes an account at Admin level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Uncanny Automator the fix is 6.3: builds <= 6.2 are affected, anything from 6.3 onward is not.

Remediation

Update to version 6.3, or a newer patched version

How does WordSec protect against this?

An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Uncanny Automator 6.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-13838https://www.wordfence.com/threat-intel/vulnerabilities/id/29eeac86-6b33-49e6-a7e1-c80dee383d6fhttps://nvd.nist.gov/vuln/detail/CVE-2024-13838

Related records

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