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.
History

Thu, 12 Nov 2026 16:30:00 +0000

Type Values Removed Values Added
First Time appeared John-dagelmore
John-dagelmore wpspeed – Wordpress Speed, Cache & Performance Optimization (core Web Vitals, Pagespeed 100)
Wordpress-extensions
Wordpress-extensions wpspeed
Vendors & Products John-dagelmore
John-dagelmore wpspeed – Wordpress Speed, Cache & Performance Optimization (core Web Vitals, Pagespeed 100)
Wordpress-extensions
Wordpress-extensions wpspeed

Sun, 08 Nov 2026 06:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Sat, 07 Nov 2026 09:30:00 +0000

Type Values Removed Values Added
Description 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.
Title WPSpeed <= 2.6.10 - Authenticated (Subscriber+) Stored Cross-Site Scripting via User Nickname/Display Name
Weaknesses CWE-79
References
Metrics cvssV3_1

{'score': 6.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published: 2026-11-07T09:25:46.871Z

Updated: 2026-11-07T18:06:03.788Z

Reserved: 2026-10-28T19:51:16.327Z

Link: CVE-2026-118784

cve-icon Vulnrichment

Updated: 2026-11-07T18:00:50.259Z

cve-icon NVD

Status : Deferred

Published: 2026-11-07T10:17:06.970

Modified: 2026-11-07T18:17:13.860

Link: CVE-2026-118784

cve-icon Redhat

No data.