WP AutoKeyword
wp-autokeyword · plugin
Known security vulnerabilities for WP AutoKeyword. Find out in seconds which version runs on your site with WP Lens.
4 known vulnerabilities
1 critical · 3 exploitable without logging in · 4 with no official fix seen · latest Jun 6, 2025
Before you install
Do not install
- 4 records show no fix in the latest wordpress.org release.
- 3 records needing no login published in the last two years.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Listed on wordpress.org · latest 1.0 · last updated Apr 28, 2025 · 200+ installs
wordpress.org status checked on Nov 19, 2026
Vulnerabilities
- Critical 9.3
CVE-2025-31579unauthenticatedno fix seen
WordPress WP AutoKeyword plugin <= 1.0 - SQL Injection vulnerability
- High 7.1
CVE-2025-32582unauthenticated · needs a clickno fix seen
WordPress WP AutoKeyword Plugin <= 1.0 - Cross Site Scripting (XSS) vulnerability
- Medium 5.4
CVE-2025-31870login requiredno fix seen
WordPress WP AutoKeyword plugin <= 1.0 - Arbitrary Content Deletion vulnerability
- Medium 5.3
CVE-2025-28997unauthenticatedno fix seen
WordPress WP AutoKeyword plugin <= 1.0 - Broken Access Control Vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS). The record lists the latest wordpress.org release (1.0) as affected.
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.