CVE-2026-9010 PixelYourSite CVE debrief

Who should care

Administrators and users of the Boost plugin for WordPress should be aware of this vulnerability and take immediate action to protect their installations. This includes updating the plugin to a version that is not vulnerable, implementing additional security measures to monitor and protect against SQL injection attacks, and regularly reviewing and updating plugins and themes to prevent vulnerabilities. Security teams should also review their asset inventory and ensure that compensating controls are in place for exposed systems.

Technical summary

The Boost plugin for WordPress is vulnerable to time-based SQL Injection via the 'current_url' and 'user_name' parameters in versions up to, and including, 2.0.3. This vulnerability allows unauthenticated attackers to append additional SQL queries into existing queries, potentially leading to sensitive information disclosure. The vulnerability is due to insufficient escaping on user-supplied parameters and a lack of sufficient preparation on existing SQL queries. This issue affects WordPress installations using the Boost plugin, particularly those with user-supplied input not properly sanitized.

Defensive priority

High

Recommended defensive actions

• Update the Boost plugin to a version that is not vulnerable
• Implement additional security measures to monitor and protect against SQL injection attacks
• Regularly review and update plugins and themes to prevent vulnerabilities
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• 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 CVE record was published on 2026-05-20T04:16:59.703Z and was last modified on 2026-05-20T13:54:54.890Z. The NVD entry is currently Deferred. This information is based on the supplied source corpus and may not reflect the current status of the vulnerability. Defenders should verify the status and affected scope with the vendor or through CVE.org for the most up-to-date information.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.