What is the CVSS score of CVE-2025-5487?

CVE-2025-5487 has a CVSS 3.1 base score of 7.2 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of PHP are affected by CVE-2025-5487?

The AutomatorWP plugin contains a SQL injection vulnerability affecting WordPress sites running versions up to 5.2.3.

How to fix or mitigate CVE-2025-5487?

Within 24 hours: Audit all user accounts with Administrator access in WordPress; document which users have legitimate need for this role. Within 7 days: Implement network-level or WAF rules to restrict admin access to trusted IP ranges; disable the AutomatorWP plugin if not actively required for operations. Within 30 days: Monitor vendor communications for patch availability; evaluate alternative automation solutions; conduct database access audit to identify any suspicious queries in logs.

PHP CVE-2025-5487

EUVD-2025-18321 HIGH

SQL Injection (CWE-89)

2025-06-14 security@wordfence.com

WordPress SQLi PHP Information Disclosure

7.2

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.2 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

EUVD ID Assigned

Mar 14, 2026 - 21:53 euvd

EUVD-2025-18321

Analysis Generated

Mar 14, 2026 - 21:53 vuln.today

CVE Published

Jun 14, 2025 - 07:15 nvd

HIGH 7.2

DescriptionCVE.org

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.

AnalysisAI

AutomatorWP plugin for WordPress versions up to 5.2.3 contains a time-based SQL injection vulnerability in the field_conditions parameter that allows authenticated administrators and higher-privileged users to extract sensitive database information through insufficient input escaping and lack of prepared statements. While the CVSS score of 7.2 is moderately high, exploitation requires administrator-level access, significantly limiting real-world attack surface; no active exploitation in the wild has been confirmed at this time.

Technical ContextAI

The vulnerability exists in the AutomatorWP plugin (CPE: wp:automatormwp), a WordPress no-code automation platform that processes user-supplied parameters for workflow conditions. The root cause is CWE-89 (SQL Injection) stemming from inadequate escaping of the field_conditions parameter and failure to use parameterized queries/prepared statements. When users configure automation rules through the plugin's UI, input values are concatenated directly into SQL queries rather than being passed as bound parameters. Time-based SQL injection techniques (using SLEEP() or similar database delay functions) allow attackers to infer database structure and contents through response timing analysis, bypassing simple input validation or WAF filters that rely on pattern matching.

RemediationAI

Upgrade AutomatorWP plugin to version 5.2.4 or later when available; priority: High for multi-user sites; Medium for single-admin sites; vendor_advisory: Monitor WordPress plugin repository and Code Potent security advisories for patched version release Workaround: Restrict field_conditions automation configuration to trusted administrators only; remove delegated automation rights from Author and Contributor roles; priority: Immediate if patch unavailable Mitigation: Implement WordPress security hardening: disable plugin auto-updates if not trusted, enforce strong administrator password policies, enable audit logging of automation rule changes, implement database activity monitoring for time-based query patterns; priority: Ongoing defense-in-depth Detection: Search database logs for SQL SLEEP() or benchmark-function calls in conjunction with AutomatorWP operations; monitor for unusual automated database queries originating from plugin execution; priority: High