Skip to main content
Vulnerability Database/CVE-2026-110375

CVE-2026-110375: Download Monitor XSS Vulnerability

CVE-2026-110375 is a stored cross-site scripting vulnerability in WP Chill Download Monitor plugin that allows attackers to inject malicious scripts. This post covers technical details, affected versions through 5.3.3, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-110375 Overview

CVE-2026-110375 is a stored Cross-Site Scripting (XSS) vulnerability in the WP Chill Download Monitor plugin for WordPress [CWE-79]. The flaw affects all versions of the download-monitor plugin up to and including 5.3.3. An authenticated attacker with low privileges can inject malicious JavaScript that persists in the application and executes in the browser of any user who views the affected page. Successful exploitation requires user interaction and can lead to session theft, administrative action abuse, and content tampering within the WordPress admin or front-end context.

Critical Impact

A low-privileged authenticated user can store malicious scripts that execute against higher-privileged users, enabling scope changes across the WordPress site.

Affected Products

  • WP Chill Download Monitor plugin for WordPress
  • All versions from unspecified initial release through 5.3.3
  • WordPress sites using the download-monitor plugin for file distribution

Discovery Timeline

  • 2026-10-15 - CVE-2026-110375 published to the National Vulnerability Database (NVD)
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-110375

Vulnerability Analysis

The vulnerability is a stored Cross-Site Scripting flaw in the Download Monitor plugin. The plugin fails to properly neutralize user-supplied input before rendering it within web page output. An authenticated attacker submits crafted input containing HTML or JavaScript payloads through plugin-exposed fields. The server persists the input and later renders it without adequate output encoding or sanitization.

When another user, typically an administrator or editor, views the affected page, the browser parses and executes the injected script within the site origin. The scope change indicates that the executed script can affect resources beyond the vulnerable component itself, such as the WordPress admin interface. Impact includes session hijacking, exfiltration of authenticated cookies, redirection to attacker-controlled sites, and silent execution of privileged WordPress REST or admin actions.

Root Cause

The root cause is improper neutralization of input during web page generation [CWE-79]. The plugin accepts user input through its download management interfaces and stores it in the WordPress database. On render, the plugin fails to apply context-appropriate escaping functions such as esc_html(), esc_attr(), or wp_kses() before output. The absence of sanitization on write and escaping on read allows arbitrary HTML and script content to persist and execute.

Attack Vector

Exploitation requires network access to the WordPress site, low-privilege authentication, and user interaction from a victim who loads the affected page. The attacker authenticates as a user with permission to interact with the Download Monitor plugin. The attacker submits a payload containing a JavaScript event handler or <script> tag in a plugin field that is later rendered in the admin or public context. When a higher-privileged user visits the page, the stored payload executes with their session privileges. Refer to the Patchstack XSS Vulnerability Report for additional technical context.

Detection Methods for CVE-2026-110375

Indicators of Compromise

  • Stored content in the WordPress wp_posts, wp_postmeta, or plugin-specific tables containing <script> tags, javascript: URIs, or inline event handlers such as onerror= or onload=
  • Outbound HTTP requests from administrator browsers to unexpected external domains shortly after loading a Download Monitor admin page
  • Unexpected creation of new administrator accounts or modification of WordPress options following admin page views
  • Web server access logs showing POST requests to Download Monitor endpoints containing encoded script payloads

Detection Strategies

  • Scan plugin database tables for HTML and JavaScript artifacts in fields that should contain only plain text or URLs
  • Deploy a Web Application Firewall (WAF) rule set that identifies XSS payloads targeting WordPress plugin parameters
  • Enable WordPress audit logging to track content changes made by low-privilege roles against Download Monitor objects
  • Correlate authenticated session anomalies with recent views of Download Monitor-managed pages

Monitoring Recommendations

  • Monitor WordPress administrator browser sessions for unexpected JavaScript execution using Content Security Policy (CSP) violation reports
  • Alert on new or modified Download Monitor entries created by users below the Administrator role
  • Track changes to the wp_users table and privileged wp_options keys following admin access to download pages
  • Review HTTP referer and request patterns for signs of forced interaction with crafted download URLs

How to Mitigate CVE-2026-110375

Immediate Actions Required

  • Identify all WordPress installations running the Download Monitor plugin at version 5.3.3 or earlier
  • Restrict access to Download Monitor administrative features to trusted accounts only until a patched release is applied
  • Audit existing download entries for stored HTML or JavaScript content and remove any suspicious payloads
  • Rotate administrator credentials and invalidate active sessions if exploitation is suspected

Patch Information

At the time of publication, review the Patchstack XSS Vulnerability Report for the latest fixed version information from WP Chill. Upgrade to a version later than 5.3.3 once released by the vendor and verify the plugin changelog references CVE-2026-110375.

Workarounds

  • Deploy a WAF rule that blocks requests containing <script, javascript:, or inline event handler patterns against /wp-admin/ endpoints associated with Download Monitor
  • Enforce a strict Content Security Policy that disallows inline scripts in the WordPress admin interface
  • Temporarily deactivate the Download Monitor plugin on sites where low-privilege authenticated users exist
  • Limit plugin interaction to the Administrator role through capability management plugins until a patch is applied
bash
# Example WordPress CLI commands to audit and disable the vulnerable plugin
wp plugin list --name=download-monitor --fields=name,status,version
wp plugin deactivate download-monitor
# After vendor patch is released:
wp plugin update download-monitor

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.