CVE-2026-2269
Server-Side Request Forgery in Uncanny Automator Plugin Enables RCE
Publication date: 2026-03-03
Last updated on: 2026-03-03
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| uncanny_automator | uncanny_automator | to 7.0.0.3 (inc) |
| uncanny_automator | uncanny_automator | 7.1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-434 | The product allows the upload or transfer of dangerous file types that are automatically processed within its environment. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know
Can you explain this vulnerability to me?
The Uncanny Automator WordPress plugin, up to version 7.0.0.3, is vulnerable to Server-Side Request Forgery (SSRF) via its download_url() function.
This vulnerability allows authenticated users with Administrator-level access or higher to make web requests from the web application to arbitrary locations.
Attackers can use this to query and modify information from internal services.
Additionally, the plugin stores the contents of remote files on the server, which can be exploited to upload arbitrary files to the affected site’s server, potentially enabling remote code execution.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized internal network access and data manipulation.
An attacker with administrator privileges can make the server send requests to arbitrary locations, potentially accessing sensitive internal services.
The ability to upload arbitrary files to the server may lead to remote code execution, allowing attackers to run malicious code on the affected site.
Overall, this can compromise the confidentiality, integrity, and availability of the affected system.