# CVE-2025-9539: Missing authorization in AutomatorWP – Automator plugin for no-code automations, webhooks & custom integrations in WordPress

> Authenticated subscribers can create arbitrary automations leading to remote code execution or privilege escalation due to missing capability checks.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Sep 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-w4r4-wvrh-xgqg

## What is CVE-2025-9539?

CVE-2025-9539 is a high-severity missing authorization vulnerability in rubengc AutomatorWP – Automator plugin for no-code automations, webhooks & custom integrations in WordPress, published on 9 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The AutomatorWP – Automator plugin for no-code automations, webhooks & custom integrations in WordPress plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the automatorwp_ajax_import_automation_from_url function in all versions up to, and including, 5.3.6. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create arbitrary automations, which can lead to Remote Code Execution or Privilege escalation once such automation is activated by the administrator

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2025-9539?


## How do I fix CVE-2025-9539?

No fix has been published for CVE-2025-9539 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-9539 being exploited?

There is no known exploitation of CVE-2025-9539 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9539 and fix it if it is affected.

What it is: CVE-2025-9539 is a high-severity missing authorization vulnerability in rubengc AutomatorWP – Automator plugin for no-code automations, webhooks & custom integrations in WordPress, published on 9 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-9539 in the wild and no public exploit code.

Affected product: rubengc AutomatorWP – Automator plugin for no-code automations, webhooks & custom integrations in WordPress. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-9539/ (Markdown: https://insights.sbomify.com/CVE-2025-9539/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9539
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9539
- OSV: https://osv.dev/vulnerability/CVE-2025-9539

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-9539/
Summaries are generated and may contain mistakes; the official description above is the record.