CVE-2026-0734
Stored XSS in WP Allowed Hosts Plugin Affects Multi-Site
Publication date: 2026-01-14
Last updated on: 2026-01-14
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | wp_allowed_hosts | to 1.0.8 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-0734 is a Stored Cross-Site Scripting (XSS) vulnerability in the WP Allowed Hosts WordPress plugin (up to version 1.0.8). It occurs because the plugin does not properly sanitize or escape input provided via the 'allowed-hosts' parameter. Authenticated users with administrator-level access or higher can inject malicious scripts into pages. These scripts execute whenever a user accesses the affected page. This vulnerability specifically affects multisite WordPress installations or installations where the 'unfiltered_html' capability is disabled.
How can this vulnerability impact me? :
This vulnerability allows an attacker with administrator-level access to inject arbitrary web scripts into pages. These scripts can execute in the context of users visiting those pages, potentially leading to theft of user credentials, session hijacking, or other malicious actions. Since it is a stored XSS, the malicious code persists and affects multiple users. The impact is limited to multisite installations or those with 'unfiltered_html' disabled, but it can compromise site security and user trust.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by reviewing the 'allowed-hosts' parameter in the WP Allowed Hosts plugin settings on multisite WordPress installations where unfiltered_html is disabled. Since the vulnerability involves stored cross-site scripting via this parameter, you can check for suspicious or unexpected script tags or payloads in the allowed hosts configuration. Additionally, monitoring HTTP requests and responses for injected scripts on pages accessible by users can help detect exploitation. Specific commands are not provided in the resources, but inspecting the WordPress database options 'allowed-hosts' and 'allowed-hosts-regex' via WP-CLI commands such as `wp option get allowed-hosts` or `wp site option get allowed-hosts` (for multisite) can help identify malicious entries. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the WP Allowed Hosts plugin to a version later than 1.0.8 where the vulnerability is fixed (if available). If an update is not available, restrict administrator access to the plugin settings page to trusted users only, as exploitation requires administrator-level access. Review and sanitize the 'allowed-hosts' parameter to remove any injected scripts or suspicious entries. Disable regex matching if not necessary, as it increases risk due to lack of sanitization. Also, ensure that the WordPress installation is multisite and that unfiltered_html is enabled only if necessary, as the vulnerability affects multisite installations with unfiltered_html disabled. [1, 3]