A high-severity security flaw, tracked as CVE-2024-47374 (CVSS score 7.2), in the LiteSpeed Cache plugin for WordPress could allow attackers to execute arbitrary JavaScript.<\/p>\n\n\n\n
The vulnerability is a stored cross-site scripting (XSS) issue impacting versions up to 6.5.0.2.<\/p>\n\n\n\n
This LiteSpeed Cache plugin is an all-in-one site acceleration tool, offering server-level caching and optimization features. It supports WordPress Multisite and is compatible with popular plugins like WooCommerce, bbPress, and Yoast SEO. LiteSpeed Cache<\/a> has over six million active installations, for this reason, site admins must address the issue as soon as possible.
The vulnerability\u00a0was originally reported by\u00a0TaiYou<\/a>\u00a0to the\u00a0Patchstack bug bounty program for WordPress<\/a>.\u00a0<\/em><\/p>\n\n\n\n
“This plugin suffers from unauthenticated stored XSS vulnerability. It could allow any unauthenticated user from stealing sensitive information to, in this case, privilege escalation on the WordPress site by performing a single HTTP request.” reads<\/a> the advisory.<\/em><\/p>\n\n\n\n
The vulnerability was addressed in version 6.5.1 on September 25, 2024.
“We recommend applying escaping and sanitization to any message that will be displayed as an admin notice. Depending on the context of the data, we recommend using\u00a0sanitize_text_field<\/a>\u00a0to sanitize value for HTML output (outside of HTML attribute) or\u00a0esc_html<\/a>. For escaping values inside of attributes, you can use the\u00a0esc_attr\u00a0<\/a>function.” concludes the report. “We also recommend applying a proper permission or authorization check to the registered rest route endpoints.”<\/em>
In early September, the developer behind the LiteSpeed Cache plugin addressed<\/strong><\/a> another unauthenticated account takeover vulnerability, tracked as CVE-2024-44000 (CVSS score: 7.5), that can allow any visitor to gain access to logged-in users and potentially escalate privileges to the Administrator level. An attacker can exploit this vulnerability to upload malicious plugins.<\/p>\n\n\n\n
\u201cThe vulnerability exploits an HTTP response headers leak on the debug log file which also leaks the \u201cSet-Cookie\u201d header after the users perform a login request.\u201d reads the
report<\/a> published by Patchstack. \u201cThe main vulnerable code exists on the function
ended<\/code>\u201c<\/em><\/p>\n\n\n\n
Pierluigi Paganini<\/strong><\/a><\/p>\n\n\n\n
Follow me on Twitter: @securityaffairs<\/strong><\/a> and Facebook<\/strong><\/a> and Mastodon<\/a><\/p>\n\n\n\n
(<\/strong>SecurityAffairs<\/strong><\/a>\u00a0\u2013<\/strong>\u00a0hacking, WordPress)<\/strong><\/p>\n\n\n\n