dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-5487

HIGH · 7.2 CVSS v3.1 Published 2025-06-14
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 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.

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 AutomatorWP WordPress plugin versions up to 5.2.3 contains a time-based SQL injection vulnerability in the field_conditions parameter. The plugin fails to properly escape user-supplied input and lacks sufficient prepared statements, allowing authenticated administrators (or configured lower roles) to inject malicious SQL queries and extract sensitive data from the database.

MitigationUpdate the AutomatorWP plugin to the latest available version (5.2.4 or later) which contains the patched SQL query handling. If immediate update is not possible, disable the affected functionality or restrict user access to the automation features until the patch can be applied.

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. Verify AutomatorWP plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for AutomatorWP in the list. Note the installed version displayed next to the plugin name.
    Affected if AutomatorWP plugin is present in the plugins list
  2. Check installed version against affected range
    Compare the installed version number to the affected range: any version up to and including 5.2.3 is vulnerable. Versions 5.2.4 and later are patched.
    Affected if Installed version is 5.2.3 or lower
  3. Confirm automation features are accessible
    Verify that AutomatorWP automation features (automations, recipes, or triggers using field_conditions) are active on the site. Check if any automations exist that utilize conditional logic with user-supplied field values.
    Affected if AutomatorWP automations with conditional field_conditions are active and accessible to users
  4. Review user role permissions
    Check WordPress user roles that have access to AutomatorWP automation features. Go to Users > Users or Users > User Roles in the AutomatorWP settings. By default administrators have access, but lower roles may be configured.
    Affected if Any authenticated user role (administrator or configured lower role) can access and configure automations with field_conditions

If the installed version is 5.2.3 or lower and any authenticated user with automation access exists on the site, the environment is affected by this SQL injection vulnerability.

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 AutomatorWP plugin to the latest available version (5.2.4 or later) which contains the patched SQL query handling. If immediate update is not possible, disable the affected functionality or restrict user access to the automation features until the patch can be applied.

Recommended fix Moderate confidence

Latest version after 5.2.3 (e.g., 5.2.4 or later)

  1. Update the AutomatorWP plugin to the latest available version from the WordPress plugin repository
  2. After updating, verify the plugin is working correctly by testing any automated recipes that use the field_conditions parameter
  3. Ensure all administrators and users with access to the plugin's automation features are trusted, as the vulnerability requires authenticated access

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5487 — 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-2025-5487 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