● High · CVSS 7.2

How to Fix CVE-2026-2269: Unrestricted file upload in Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin

Q: What is the CVSS score for CVE-2026-2269?

7.2 (High). Vector: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`.

Q: Where is the official advisory for CVE-2026-2269?

The vendor advisory is at [https://www.wordfence.com/threat-intel/vulnerabilities/id/80848de3-a772-4078-aa04-29e1d6e3ff73?source=cve](https://www.wordfence.com/threat-intel/vulnerabilities/id/80848de3-a772-4078-aa04-29e1d6e3ff73?source=cve). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-2269.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-2269 is a unrestricted file upload in uncannyowl Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	7.2 (High)
Actively exploited?	No public listing in CISA KEV
Affected	Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin 0 to <=7.0.0.3
Fixed in	See vendor advisory
Type (CWE)	CWE-434 Unrestricted Upload of File with Dangerous Type

What is CVE-2026-2269?

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, 7.0.0.3 via the download_url() function. 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. Additionally, the plugin stores the contents of the remote files on the server, which can be use to upload arbitrary files on the affected site's server which may make remote code execution possible. The CVSS base score is 7.2 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://www.wordfence.com/threat-intel/vulnerabilities/id/80848de3-a772-4078-aa04-29e1d6e3ff73?source=cve.

Am I affected?

Check the version of Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin you are running and compare it against the Affected row above (Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin 0 to <=7.0.0.3). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin 2>/dev/null | grep -i ^Version
rpm -q uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin 2>/dev/null
command -v uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin >/dev/null && uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin" 2>$null

How to fix CVE-2026-2269

Upgrade Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin
dpkg -s uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin -y
# or for older releases:
sudo yum update uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin -y
rpm -q uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin

SUSE / openSUSE


sudo zypper refresh
sudo zypper update uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin
rpm -q uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin

PHP / Composer


composer update uncannyowl/uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin 2>/dev/null || composer update
composer show | head -20

WordPress


# Update via WP-CLI
wp plugin update --all
wp core update

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-2269 affecting Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-2269-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-2269 affecting Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-2269-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin 2>/dev/null | grep -i ^Version || echo "uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin || echo "uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-2269-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin /etc/uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin.d /etc/uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin
elif command -v yum >/dev/null; then
    yum update -y uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin
elif command -v zypper >/dev/null; then
    zypper --non-interactive update uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-2269" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-2269"

Disable the affected service (Linux)


sudo systemctl stop uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin 2>/dev/null || true
sudo systemctl disable uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin 2>/dev/null | grep -i ^Version
rpm -q uncanny-automator-easy-automation-integration-webhooks-workflow-builder-plugin 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*Uncanny Automator – Easy Automation, Integration, Webhooks & Workflow Builder Plugin*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-34941: Out-of-bounds read in wasmtime — Out-of-bounds read in wasmtime
How to Fix CVE-2026-22885: Path Traversal in SmartServer IoT — Path Traversal in SmartServer IoT
How to Fix CVE-2026-33732: Critical Vulnerability in srvx , Critical Vulnerability in srvx
How to Fix CVE-2026-23496: Access Control Bypass in pimcore , Access Control Bypass in pimcore
How to Fix CVE-2026-44993: Incomplete List of Disallowed Inputs in OpenClaw , Incomplete List of Disallowed Inputs in OpenClaw

Is CVE-2026-2269 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-2269?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-2269?

7.2 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H.

Where is the official advisory for CVE-2026-2269?

The vendor advisory is at https://www.wordfence.com/threat-intel/vulnerabilities/id/80848de3-a772-4078-aa04-29e1d6e3ff73?source=cve. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-2269.

References

Official vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/80848de3-a772-4078-aa04-29e1d6e3ff73?source=cve
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2269
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://plugins.trac.wordpress.org/changeset/3471238/

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*