PatchSiren cyber security CVE debrief
CVE-2026-15445 cleverplugins CVE debrief
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 vulnerability allows authenticated attackers with administrator-level access and above to append additional SQL queries into existing queries, enabling them to extract sensitive information from the database. The vulnerability exists because esc_sql() and sanitize_text_field() do not neutralize SQL keywords, commas, parentheses, or subquery syntax in an unquoted ORDER BY context. Affected deployments should prioritize patching, while defenders should verify and monitor for potential exploitation.
- Vendor
- cleverplugins
- Product
- SEO Booster
- CVSS
- MEDIUM 4.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-16
- Original CVE updated
- 2026-07-16
- Advisory published
- 2026-07-16
- Advisory updated
- 2026-07-16
Who should care
Administrators and users with high privileges on WordPress installations using the SEO Booster plugin should be aware of this vulnerability and take immediate action to protect their sites.
Technical summary
The vulnerability exists in the SEO Booster plugin for WordPress, specifically in the handling of the 'orderby' parameter. Despite the application of esc_sql() and sanitize_text_field(), these functions do not neutralize SQL keywords, commas, parentheses, or subquery syntax in an unquoted ORDER BY context. This allows authenticated attackers with administrator-level access and above to append additional SQL queries into existing queries, enabling them to extract sensitive information from the database.
Defensive priority
High
Recommended defensive actions
- Update the SEO Booster plugin to a version that fixes the SQL injection vulnerability.
- Limit access to the plugin's settings and functionality to only trusted users.
- Monitor database activity for suspicious queries.
- Consider implementing a web application firewall (WAF) to detect and prevent SQL injection attacks.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
Evidence notes
The vulnerability was reported by [email protected]. The CVE record was published on 2026-07-16T05:16:18.633Z and has not been modified since then. The NVD entry is currently in the 'Received' status. Evidence is limited to public sources and may not reflect the full scope or impact of the vulnerability. Defenders should verify affected deployments and review official advisories for specific guidance. Limited source detail suggests additional verification may be required to confirm affected scope and severity.
Official resources
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-07-16T05:16:18.633Z and has not been modified since then. The NVD entry is currently in the 'Received' status.