dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-2269

HIGH · 7.2 CVSS v3.1 Published 2026-03-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 leveraged to upload arbitrary files on the affected site's server which may make remote code execution possible.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Uncanny Automator WordPress plugin contains an SSRF vulnerability in the download_url() function, allowing authenticated administrators to make arbitrary web requests from the server. The additional capability to store downloaded remote files enables arbitrary file upload, which can lead to remote code execution.

MitigationUpdate the Uncanny Automator plugin to version 7.0.0.4 or later. Until patched, limit administrator access to trusted personnel only and monitor server outgoing network requests for suspicious activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Uncanny Automator plugin is installed
    Run 'wp plugin list' via WP-CLI, check the plugins directory via FTP, or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if Uncanny Automator appears in the list of installed plugins
  2. Identify the installed plugin version
    Check the plugin header in the main plugin file (usually wp-content/plugins/uncanny-automator/uncanny-automator.php) for the 'Version' field, or run 'wp plugin get uncanny-automator' via WP-CLI
    Affected if The version number is lower than 7.0.0.4 (e.g., 7.0.0.3, 6.x.x.x, etc.)
  3. Verify administrator access exists on the site
    Check user roles via WP-CLI with 'wp user list --role=administrator' or review user capabilities in WordPress admin under Users
    Affected if At least one user with Administrator role exists or has administrative capabilities
  4. Check if the download_url feature is accessible
    The vulnerable download_url() function is invoked through the plugin's UI. Navigate to the plugin settings or recipe creation areas where remote file download actions may be configured, or inspect plugin logs for download_url activity
    Affected if The plugin UI allows configuring actions that fetch remote URLs (the download_url function is present and executable)
  5. Inspect for recently created suspicious files
    Check wp-content/uploads/ and other writable directories for unfamiliar PHP files or files with unusual extensions created recently, using 'find wp-content/uploads -name "*.php" -mtime -7' or similar
    Affected if Unexpected PHP files or uploaded content appears in directories without corresponding user uploads

The environment is affected if Uncanny Automator plugin versions below 7.0.0.4 are installed AND at least one user with administrator privileges exists, as the vulnerability requires admin authentication to exploit the download_url function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Uncanny Automator plugin to version 7.0.0.4 or later. Until patched, limit administrator access to trusted personnel only and monitor server outgoing network requests for suspicious activity.

Recommended fix High confidence

Uncanny Automator version greater than 7.0.0.3 (check WordPress plugin repository for latest stable release)

  1. 1. Log in to the WordPress admin dashboard with Administrator-level access.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate 'Uncanny Automator' in the plugin list.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, download the latest version from the WordPress plugin repository (plugins.trac.wordpress.org) and upload it manually via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the new version number is greater than 7.0.0.3.
  7. 7. Review any uploaded files in the wp-content/uploads/automator directory to ensure no malicious files were uploaded during exploitation.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2269 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2269 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data