CVE-2026-105394 in Asset CleanUp Page Speed Booster Plugin
Summary
by MITRE • 11/22/2026
The Asset CleanUp: Page Speed Booster WordPress plugin before 1.4.0.7 does not restrict which origins it reflects into its cross-origin resource sharing response headers and pairs the reflected origin with credentialed access, allowing a page on a related origin to read a logged-in user's authenticated content across origins.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 11/22/2026
The vulnerability identified in Asset CleanUp: Page Speed Booster versions prior to 1.4.0.7 represents a critical misconfiguration of Cross-Origin Resource Sharing (CORS) policies that undermines the security boundaries established by modern web browsers. This plugin, widely used for optimizing WordPress sites by minifying and combining CSS and JavaScript files, failed to implement strict validation mechanisms when handling cross-origin requests. Specifically, the application logic reflected the Origin header from incoming HTTP requests directly into the Access-Control-Allow-Origin response header without verifying whether that origin was legitimate or pre-approved. This behavior effectively allowed any website hosted on a different domain to request resources from the vulnerable WordPress site and receive them with explicit permission for cross-domain access.
The severity of this flaw is significantly amplified by its interaction with credentialed requests. The plugin configured the Access-Control-Allow-Credentials header to true, indicating that the server permits cookies or other authentication credentials to be included in cross-origin requests. When a user visits an attacker-controlled malicious website while simultaneously logged into the vulnerable WordPress site via their browser session, the browser will automatically include the user's authentication cookies with any request sent from the malicious page to the WordPress domain due to this configuration. Because the server reflects back the origin of the malicious page in its CORS headers and allows credentials, the browser interprets the response as safe for cross-origin consumption by that specific attacker-controlled script.
This combination creates a severe Cross-Site Request Forgery (CSRF) vector combined with data exfiltration capabilities. An adversary can craft a simple HTML page containing JavaScript code that issues an XMLHttpRequest or fetch call to endpoints within the vulnerable WordPress installation, such as those serving dynamic content, user profiles, or administrative settings. Since the browser attaches the victim's session cookies automatically and accepts the reflected CORS headers, the malicious script gains full read access to the authenticated response data returned by the server. This allows the attacker to harvest sensitive information belonging to logged-in users, including personal details, private posts, comments, or potentially administrative configurations depending on which endpoints are accessible via the exposed API routes handled by the plugin.
From a classification perspective, this vulnerability aligns with CWE-942, which describes Permissive Cross-Origin Resource Sharing, and specifically highlights the dangerous practice of reflecting user-supplied input into CORS headers without validation. It also maps to MITRE ATT&CK technique T1505.003, Server Software Component: Web Shell or similar server-side components that can be abused for data access, although in this context it is more accurately described as an abuse of web application configuration leading to unauthorized information disclosure (T1530). The flaw exploits the trust relationship between browsers and servers regarding origin validation, bypassing the Same-Origin Policy which is designed to prevent malicious sites from reading sensitive content from other sites.
Mitigation for this issue requires immediate updates to version 1.4.0.7 or later of the Asset CleanUp plugin where these CORS handling mechanisms were corrected. Administrators should ensure that their WordPress installations are fully patched and that all plugins are kept up to date with security releases provided by vendors. In environments where updating is not immediately feasible, temporary mitigations include configuring web server rules such as Nginx or Apache directives to explicitly deny requests containing an Origin header if the site does not intend to support cross-origin resource sharing for public assets. Additionally, implementing a Content Security Policy (CSP) with strict default-src and script-src directives can help mitigate the impact by preventing unauthorized scripts from executing on pages that might be compromised through other vectors, although CSP alone cannot fix the underlying CORS misconfiguration if credentials are being leaked via API endpoints. Regular security audits of plugin configurations should include verification of HTTP response headers to ensure they adhere to least-privilege principles regarding cross-origin access.