Technical impact
Drupal Stage File Proxy has an improper neutralization of input during web page generation. The flaw allows malicious scripts to be injected into pages served by the module, leading to client‑side code execution. If an attacker can supply or influence input that is rendered by the proxy, they can execute arbitrary JavaScript in the victim’s browser, potentially hijacking sessions, exfiltrating data, or redirecting users to malicious sites. The vulnerability is a classic cross‑site scripting weakness (CWE‑79).
Affected Systems
Impact is limited to installations of Drupal Stage File Proxy. All versions from 0.0.0 through 3.1.7 and from 4.0.0 through 4.0.1 are affected. The module is commonly used to proxy media files from remote hosts within Drupal sites.
Risk and Exploitability
Because the flaw is client‑side, it can be triggered by any user visiting a page that includes proxy‑served content. The CVSS score is 6.5, indicating moderate severity. No authentication or privileged context is required. The EPSS score of 0.00157 indicates a very low exploitation probability, and the vulnerability is not listed in the CISA KEV catalog, but the ability to run arbitrary JavaScript makes it high impact. The attacker only needs to cause a victim to view a proxy page containing crafted input, so exploitation is straightforward for anyone with knowledge of the affected module. Institutions should treat this as a high‑risk issue pending patch.