# CVE-2025-5487: AutomatorWP <= 5.2.5 - Authenticated (Administrator+) SQL Injection via field_conditions

> Authenticated administrators can exploit SQL injection in AutomatorWP to extract sensitive database information via the field_conditions parameter.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jun 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2pff-264c-2hqm

## What is CVE-2025-5487?

CVE-2025-5487 is a high-severity SQL injection vulnerability in rubengc AutomatorWP – Automator plugin for no-code automations, webhooks & custom integrations in WordPress, published on 14 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The AutomatorWP – Automator plugin for no-code automations, webhooks & custom integrations in WordPress plugin for WordPress is vulnerable to time-based SQL Injection via the field_conditions parameter in all versions up to, and including, 5.2.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.  This makes it possible for authenticated attackers, with Administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Administrators can configure the plugin to allow access to this functionality to authors and higher.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2025-5487 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5487 is a high-severity SQL injection vulnerability in rubengc AutomatorWP – Automator plugin for no-code automations, webhooks & custom integrations in WordPress, published on 14 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5487 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-5487/ (Markdown: https://insights.sbomify.com/CVE-2025-5487/index.md)
```

## Sources

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

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