{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-5487 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-5487 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-5487 is a high-severity SQL injection vulnerability in rubengc AutomatorWP – Automator plugin for no-code automations, webhooks \u0026 custom integrations in WordPress, published on 14 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-5487 and fix it if it is affected.\n\nWhat it is: CVE-2025-5487 is a high-severity SQL injection vulnerability in rubengc AutomatorWP – Automator plugin for no-code automations, webhooks \u0026 custom integrations in WordPress, published on 14 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-5487 in the wild and no public exploit code.\n\nAffected product: rubengc AutomatorWP – Automator plugin for no-code automations, webhooks \u0026 custom integrations in WordPress. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-5487/ (Markdown: https://insights.sbomify.com/CVE-2025-5487/index.md)","id":"CVE-2025-5487","markdown":"https://insights.sbomify.com/CVE-2025-5487/index.md","name":"CVE-2025-5487","record":{"aliases":["GHSA-2pff-264c-2hqm"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Authenticated administrators can exploit SQL injection in AutomatorWP to extract sensitive database information via the field_conditions parameter.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The AutomatorWP – Automator plugin for no-code automations, webhooks \u0026 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"AutomatorWP \u003c= 5.2.5 - Authenticated (Administrator+) SQL Injection via field_conditions","id":"CVE-2025-5487","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"WP Masonry \u0026 Infinite Scroll \u003c= 2.2 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2025-5488"},"packages":[],"prev":{"headline":"WP Email Debug 1.0 - 1.1.0 - Missing Authorization to Unauthenticated Privilege Escalation via Password Reset","id":"CVE-2025-5486"},"products":["AutomatorWP – Automator plugin for no-code automations, webhooks \u0026 custom integrations in WordPress"],"published":"2025-06-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["rubengc"]},"summary":"Authenticated administrators can exploit SQL injection in AutomatorWP to extract sensitive database information via the field_conditions parameter.","url":"https://insights.sbomify.com/CVE-2025-5487/"}