HomeWordPress vulnerabilitiesWPSpeed
WPSpeed vulnerabilities
WPSpeed has 1 known vulnerability in this database. The most recent published record is dated 7 Nov 2026.
- Known vulnerabilities
- 1
- Active installs
- 2,000+
- Latest version
- 2.6.11
- Last updated
- 28 Oct 2026
- Most recent
- 7 Nov 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-118784 | Medium 6.4 | Up to 2.6.10 | Fixed in a later version (latest 2.6.11) | 2 h ago |
Read the published descriptions
- CVE-2026-118784, 7 Nov 2026
- The WPSpeed plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 2.6.10 This is due to a combination of two issues in the LightImages HTML optimizer: (1) Dispatcher::runOptimize() decides whether the current request is the site's home page by comparing only the URL path from REQUEST_URI against the path of the home URL, so on a plain-permalinks install the author archive URL /?author=<ID> is treated as the home page and the LightImages optimizer runs on it; and (2) LightImages::optimize() calls html_entity_decode() across the entire serialized DOMDocument output under the default-enabled img_processing_entity_decode setting, converting any entity-encoded markup present as plain text in the page (including WordPress's rendered author title) into live HTML. This makes it possible for authenticated attackers, with Subscriber-level access and above, to store entity-encoded markup in their own nickname/display_name through the normal profile endpoint and have that markup rehydrated into executing script when any logged-out visitor loads their author archive. CVE record
What to do if you run WPSpeed
If you run WPSpeed, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WPSpeed vulnerabilities
Free. We email you when a new vulnerability is published for WPSpeed, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.