CVE-2026-15445
MediumCVSS 4.9Exploitation Probability (EPSS)
Low risk19th percentile - higher than 19% of all known CVEs
Summary
The SEO Booster plugin for WordPress is vulnerable to time-based SQL injection via the 'orderby' parameter in all versions up to and including 7.3.1. This is due to insufficient escaping and lack of proper SQL query preparation, allowing authenticated attackers with administrator-level access to append additional SQL queries.
Risk Assessment
Attackers with administrator privileges can exploit this vulnerability to extract sensitive information from the database, such as user data or passwords, posing a significant risk to organizational data security.
Recommendation
Immediately update the SEO Booster plugin to the latest available version that addresses this vulnerability, and restrict administrator access to trusted users only.
Other vulnerabilities in SEO Booster
See all- CVE-2026-15660Medium
The SEO Booster plugin for WordPress (versions up to and including 7.4.7) is vulnerable to Missing Authorization due to a missing capability check on the handle_oauth_callback() function hooked to admin_init, which processes $_GET['access_token'] and $_GET['google_email'] without verifying the caller's role. This allows authenticated attackers with Subscriber-level access and above to overwrite the seobooster_access_token, seobooster_google_email, and seobooster_gsc_sites options and delete the seobooster_needs_reauth flag by visiting a crafted /wp-admin/ URL, disrupting the Google Search Console integration and injecting attacker-chosen data into site options.
- CVE-2026-15458Medium
The SEO Booster plugin for WordPress is vulnerable to generic SQL Injection via the 'sort_field' parameter in all versions up to and including 7.3.1. This is due to insufficient escaping on the user-supplied parameter and lack of sufficient preparation on the existing SQL query.
Original NVD description (English source)
The SEO Booster plugin for WordPress is vulnerable to time-based SQL Injection via the 'orderby' parameter in all versions up to, and including, 7.3.1 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. Although esc_sql() and sanitize_text_field() are applied, neither neutralizes SQL keywords, commas, parentheses, or subquery syntax in an unquoted ORDER BY context, leaving the clause fully attacker-controlled.