Description
The WP Custom HTML Page WordPress plugin through 0.6.2 does not sanitise HTML stored through one of its custom page handlers, nor restrict it to users allowed to post unfiltered HTML, allowing users with the Author role to store JavaScript that is served unescaped at a public URL and executes for any visitor, including administrators.
Published: 2026-08-05
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The WP Custom HTML Page plugin, up to version 0.6.2, fails to sanitize or filter stored HTML in its page handlers. Users with the Author role can store arbitrary JavaScript that is served unescaped from a public URL. The unsanitized code then runs in the browsers of any site visitor, including site administrators. This stored cross‑site scripting flaw can be used to hijack sessions, steal cookies, deface the site, or redirect users to malicious sites. The vulnerability directly maps to the classic stored XSS weakness (CWE‑79).

Affected Systems

The affected product is the WordPress plugin “WP Custom HTML Page” version 0.6.2 and earlier. No specific vendor name is published, but all installations of this plugin running those versions are vulnerable if the Author role has access to the custom page editor.

Risk and Exploitability

There is no CVSS score or EPSS value available, and the flaw is not listed in CISA’s KEV catalog. Nonetheless, the flaw grants arbitrary JavaScript execution to any authenticated user with Author permissions, which is a high‑risk vector that can be easily exercised with minimal effort. The exploit conditions are straightforward: an attacker with Author privileges must submit a page containing malicious script, and the resulting URL is publicly accessible. Because the threat does not require additional software or network access, the likelihood of exploitation is high for sites that have retained insecure versions of the plugin.

Generated by OpenCVE AI on August 5, 2026 at 07:26 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the WP Custom HTML Page plugin to the latest version that includes HTML sanitization for pages created by Authors; if no newer version exists, remove the plugin entirely.
  • If removal is not viable, disable or limit the capability that allows Authors to create or edit posts that can contain unfiltered HTML, either by configuring user role settings or by applying a role‑management plugin to strip the "unfiltered_html" capability from Authors.
  • Implement a strong Content‑Security‑Policy on the WordPress site that disallows inline scripts and restricts script sources, reducing the impact of any malicious content that may surface via the plugin.

Generated by OpenCVE AI on August 5, 2026 at 07:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 05 Aug 2026 07:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-79

Wed, 05 Aug 2026 06:30:00 +0000

Type Values Removed Values Added
Description The WP Custom HTML Page WordPress plugin through 0.6.2 does not sanitise HTML stored through one of its custom page handlers, nor restrict it to users allowed to post unfiltered HTML, allowing users with the Author role to store JavaScript that is served unescaped at a public URL and executes for any visitor, including administrators.
Title WP Custom HTML Pages <= 0.6.2 - Author+ Stored XSS
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-08-05T06:00:10.810Z

Reserved: 2026-07-24T07:54:34.768Z

Link: CVE-2026-16942

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-05T07:30:16Z

Weaknesses
  • CWE-79

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