WordPress Security Bulletin: Uncanny Automator 6 Easy Automation, Integration, Webhooks & Workflow Builder Plugin plugin (CVE-2026-2269)

On this page

Security Alert Summary

The Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin plugin for WordPress contains a server-side request forgery (SSRF) vulnerability in the download_url() function affecting all versions up to and including 7.0.0.3. Authenticated users with Administrator-level access or higher can cause the site to make requests to arbitrary locations and the plugin stores remote file contents on the server, which may allow uploading arbitrary files and could lead to remote code execution on the affected host.


CVE Details

  • CVE ID: CVE-2026-2269
  • Affected component: Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin plugin for WordPress (as stated in the CVE description)
  • Affected versions: All versions up to and including 7.0.0.3
  • Published: March 3, 2026 at 2:16:10 AM UTC
  • Last modified: March 3, 2026 at 2:16:10 AM UTC
  • CVSS v3.1: Base Score 7.2, Severity: HIGH; Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
  • Authentication / Privileges / User interaction: Requires an authenticated attacker with Administrator-level access (CVSS Privileges Required: HIGH). No user interaction required (UI:N).
  • Primary impact: Confidentiality: High; Integrity: High; Availability: High
  • CWE / weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

Technical Details

The vulnerability is a server-side request forgery (SSRF) in the plugin’s download_url() function. Because the function can be controlled by an authenticated administrator-level user, it is possible to direct the application to make web requests to arbitrary destinations on behalf of the server. Those requests originate from the web application, enabling interaction with internal services that are not otherwise publicly accessible.

The plugin additionally stores the contents of the fetched remote files on the web server. That behavior can be leveraged to place arbitrary files on the site filesystem. If those stored files are placed in a web-accessible location or otherwise executed by the server, that file upload capability increases the risk that remote code execution or modification of site content or configuration could occur.

This description is based on the CVE entry: the named function is download_url(); no additional endpoints, hooks, or specific mitigation code paths are listed in the CVE JSON.


How This Could Impact Your Website

Consider a typical WordPress site with multiple users: the site owner, editors and administrators on the internal team, and external contractors or contributors who may have accounts. If an attacker leverages an administrator account (or another account with Administrator-level privileges) to exploit this SSRF, they could cause the site to query internal services (for example, internal APIs, management interfaces, or metadata endpoints) and retrieve sensitive information. That could include internal configuration data, API responses, or other confidential resources.

Because the plugin stores remote file contents on the server, an attacker could upload files that alter site content or configuration, or place files in locations that lead to code execution if server configuration permits. The combined ability to query internal services and to store remote files on the server can therefore affect confidentiality, integrity, and availability of the site and internal systems reachable from the web application.

There is also an increased risk of targeted phishing or social engineering if internal email addresses or other user data are exposed as a result of internal queries. If you’re unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review your setup.


Recommended Actions

  • Update the affected plugin as soon as a patched version is available. (No fixed version is specified in the CVE entry.)
  • Review and reduce unnecessary user roles and privileges; ensure only trusted accounts have Administrator-level access.
  • Enforce strong passwords and enable two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins from your site.
  • Monitor site activity and server logs for unusual behavior, unexpected outbound requests, or unexpected file writes.

If you’d like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.


References