CVE-2026-133471 in Fastcache by Host.it Plugininfo

Summary

by MITRE • 11/21/2026

The Fastcache by Host.it plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 's' parameter in all versions up to, and including, 1.7.14 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. This code path is only reachable when both the Light Images feature and the DOMDocument entity-decode branch are enabled (lightimgs_status = 1 and img_processing_entity_decode = 1), which reflect the default plugin configuration.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The Fastcache by Host.it WordPress plugin, specifically in versions up to and including 1.7.14, contains a critical reflected cross-site scripting vulnerability that stems from inadequate input sanitization and output escaping mechanisms. This flaw allows unauthenticated attackers to inject arbitrary web scripts into pages generated by the application. The primary vector for this attack is the 's' parameter, which fails to properly validate or encode user-supplied data before it is rendered in the browser context. Because the vulnerability results in reflected XSS, the malicious script payload is not stored on the server but rather returned immediately as part of the HTTP response when a crafted request is processed. This type of flaw typically falls under CWE-79, which classifies improper neutralization of input during web page generation, commonly known as cross-site scripting.

The operational impact of this vulnerability is significant because it enables attackers to execute arbitrary JavaScript code in the context of the victim's browser session. If an attacker can successfully trick a user into clicking on a specially crafted link containing the malicious payload within the 's' parameter, the injected script will run with the same privileges as the legitimate website. This can lead to severe consequences such as session hijacking, where the attacker steals authentication cookies or tokens to impersonate the victim; credential theft through phishing forms embedded in the page; or defacement of the site content. Furthermore, since this is a reflected attack vector, it facilitates targeted attacks against specific individuals rather than broad-scale automated exploitation, making social engineering tactics like email spoofing or malicious links on other platforms effective delivery methods for compromising user accounts associated with the WordPress installation.

A crucial technical nuance in exploiting this vulnerability lies in its conditional reachability based on the plugin's configuration settings. The code path containing the flaw is only accessible when two specific features are enabled simultaneously: the Light Images feature and the DOMDocument entity-decode branch. These correspond to the parameters lightimgs_status being set to 1 and img_processing_entity_decode also being set to 1. Importantly, these settings represent the default configuration for the plugin out of the box. This means that a significant portion of installations are vulnerable by default without requiring any manual intervention or complex setup changes from the administrator. The reliance on DOMDocument's entity decoding suggests that the vulnerability may involve bypassing standard HTML entity encoding through specific character sequences or malformed input that triggers unexpected parsing behavior within the PHP library, leading to unescaped output being sent to the client browser.

From a threat intelligence perspective, this vulnerability aligns with MITRE ATT&CK techniques related to Client-Side Injection and Web Application Attack vectors, specifically focusing on how attackers leverage web application flaws to execute code in user browsers. The lack of proper sanitization highlights a common failure in secure coding practices where developer assumptions about input safety are not enforced through rigorous validation frameworks. To mitigate this risk, administrators should immediately update the Fastcache plugin to version 1.7.15 or later, which addresses these security deficiencies by implementing robust output encoding and stricter input validation for the 's' parameter. In cases where updating is not immediately feasible, temporary workarounds might include disabling the Light Images feature or turning off the DOMDocument entity-decode branch if such options are accessible via the plugin settings, thereby removing the vulnerable code path from execution. However, relying on configuration changes as a permanent fix is discouraged due to potential functionality loss and the risk of misconfiguration; patching remains the most effective remediation strategy. Regular security audits and adherence to OWASP guidelines for input validation and output encoding are essential preventive measures against similar vulnerabilities in WordPress plugins.

Responsible

Wordfence

Reservation

11/19/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00378

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!