LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0734: WP Allowed Hosts <= 1.0.8 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'allowed-hosts' Parameter

The WP Allowed Hosts plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'allowed-hosts' parameter in all versions up to, and including, 1.0.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

MediumCVSS 4.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-0734 is a stored cross-site scripting issue in the WP Allowed Hosts WordPress plugin. It requires an attacker who already has administrator-level access. Business risk is limited but real: malicious scripts could run for users viewing affected admin/plugin pages in specific WordPress configurations.

Executive priority

Treat as a targeted WordPress hygiene issue, not an emergency. Prioritize affected multisite or hardened WordPress environments, verify plugin presence, and follow vendor guidance because sources do not name a fixed release.

Technical view

The issue is insufficient sanitization and output escaping of the 'allowed-hosts' parameter in WP Allowed Hosts versions up to 1.0.8. It is CWE-79 with CVSS 3.1 score 4.4. Sources state it affects multisite installations and installations where unfiltered_html is disabled.

Likely exposure

Exposure is likely limited to WordPress sites using WP Allowed Hosts up to 1.0.8, especially multisite deployments or sites disabling unfiltered_html. The attacker must already be administrator-level or higher.

Exploitation context

No cited source or KEV entry indicates active exploitation. Exploitation requires high privileges, but stored XSS can persist and execute when users access the affected page.

Researcher notes

The source description says versions through 1.0.8 are affected, while the provided affected metadata is sparse and marks defaultStatus as unaffected. No patch version is identified in the supplied sources. Avoid assuming broader WordPress exposure beyond the stated plugin and conditions.

Mitigation direction

  • Identify WordPress sites using WP Allowed Hosts and record installed versions.
  • Check Wordfence and plugin vendor guidance for fixed-version or remediation details.
  • Remove or disable the plugin if it is not business-required.
  • Limit administrator accounts and review recent administrator activity.
  • Apply the vendor-recommended update or configuration change when available.

Validation and detection

  • Confirm whether WP Allowed Hosts is installed on each WordPress site.
  • Verify whether the installed version is 1.0.8 or earlier.
  • Determine whether the site is multisite or has unfiltered_html disabled.
  • Review plugin settings for unexpected changes to allowed hosts.
  • Monitor WordPress administrator accounts for suspicious activity.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0734 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N1.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.4Medium
CVSS 3.1 vector shape for CVE-2026-0734Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
dfieldflWP Allowed Hosts0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.