CVE-2026-119161: HTML Forms WP plugin: stored XSS via POST param names

HIGH
Published November 18, 2026
CISO Take

The HTML Forms – Simple WordPress Forms plugin (versions up to 1.7.1) has a stored cross-site scripting flaw: unauthenticated visitors can submit a form whose POST parameter names (array keys) carry script, and that script runs when an administrator opens the Submissions tab. The flaw is rated CVSS 7.2 (high) with a changed scope, because script running in an admin session can take over the WordPress site. It is a general-purpose WordPress form plugin, not an AI/ML component, so the AI relevance is indirect and limited to sites that host AI products, model dashboards or documentation. There is no KEV listing, no public exploit and no Nuclei template, and EPSS data is not yet available, so there is no sign of active exploitation. Update to 1.7.2 or later, and review stored submissions for suspicious parameter names.

Sources:NVDWordfenceWordPress Plugin RepositoryATLAS

What is the risk?

Moderate overall risk. Exploitation needs no authentication and no special skill (AV:N/AC:L/PR:N), but it needs an administrator to view the Submissions tab, which in practice means user interaction even though the CVSS vector lists UI:N. Scope is changed (S:C), so injected script runs in the admin's browser context and can reach WordPress admin functions. Impact is limited on confidentiality and integrity (C:L/I:L), with no availability impact. There is no KEV listing, public exploit or scanner template, and EPSS data is not available. The AI/ML exposure is indirect: the plugin has no AI functionality and the risk depends on what else the WordPress site hosts.

How does the attack unfold?

Initial Access
The attacker submits a crafted POST request to a public HTML Forms endpoint with script in a parameter name.
AML.T0049
Persistence
The plugin stores the unsanitized parameter name in the submission record.
Execution
An administrator opens the Submissions tab and the injected attributes run on page load in the admin session.
AML.T0078
Impact
The script uses the admin session to create accounts, install plugins or steal session data, leading to site takeover.

What systems are affected?

PackageEcosystemVulnerable RangePatched
HTML Forms – Simple WordPress Forms Plugin——No patch

Do you use HTML Forms – Simple WordPress Forms Plugin? You're affected.

How severe is it?

CVSS 3.1
7.2 / 10
EPSS
N/A
Exploitation Status
No known exploitation
Sophistication
Trivial

What is the attack surface?

AVACPRUISCIA
AVNetwork
ACLow
PRNone
UINone
SChanged
CLow
ILow
ANone

What should I do?

1 step
  1. 1) Update HTML Forms to version 1.7.2 or later, which fixes the escaping in the admin and submission code paths. 2) Until patched, deactivate the plugin or restrict access to the Submissions tab, and avoid opening it in a privileged session. 3) Review stored submissions for POST parameter names containing HTML or script characters such as <, >, onerror or onload. 4) Apply a Content Security Policy to the WordPress admin area and a WAF rule that blocks markup in parameter names on form endpoints. 5) Use a separate low-privilege account for reviewing form submissions, enforce MFA on admin accounts, and rotate admin sessions if suspicious entries are found. 6) Check for unexpected new admin users, plugins or modified files.

How is it classified?

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001
A.6.2.6-AI system operation and monitoring
NIST AI RMF
MANAGE 2.3-Responses to previously unknown risks
OWASP LLM Top 10
LLM03-Supply Chain

Frequently Asked Questions

What is CVE-2026-119161?

The HTML Forms – Simple WordPress Forms plugin (versions up to 1.7.1) has a stored cross-site scripting flaw: unauthenticated visitors can submit a form whose POST parameter names (array keys) carry script, and that script runs when an administrator opens the Submissions tab. The flaw is rated CVSS 7.2 (high) with a changed scope, because script running in an admin session can take over the WordPress site. It is a general-purpose WordPress form plugin, not an AI/ML component, so the AI relevance is indirect and limited to sites that host AI products, model dashboards or documentation. There is no KEV listing, no public exploit and no Nuclei template, and EPSS data is not yet available, so there is no sign of active exploitation. Update to 1.7.2 or later, and review stored submissions for suspicious parameter names.

Is CVE-2026-119161 actively exploited?

No confirmed active exploitation of CVE-2026-119161 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-119161?

1) Update HTML Forms to version 1.7.2 or later, which fixes the escaping in the admin and submission code paths. 2) Until patched, deactivate the plugin or restrict access to the Submissions tab, and avoid opening it in a privileged session. 3) Review stored submissions for POST parameter names containing HTML or script characters such as <, >, onerror or onload. 4) Apply a Content Security Policy to the WordPress admin area and a WAF rule that blocks markup in parameter names on form endpoints. 5) Use a separate low-privilege account for reviewing form submissions, enforce MFA on admin accounts, and rotate admin sessions if suspicious entries are found. 6) Check for unexpected new admin users, plugins or modified files.

What systems are affected by CVE-2026-119161?

This vulnerability affects the following AI/ML architecture patterns: WordPress-hosted web front ends for AI products, Lead capture and support forms for AI services, Admin consoles sharing credentials with AI platforms.

What is the CVSS score for CVE-2026-119161?

CVE-2026-119161 has a CVSS v3.1 base score of 7.2 (HIGH).

What is the AI security impact?

Affected AI Architectures

WordPress-hosted web front ends for AI productsLead capture and support forms for AI servicesAdmin consoles sharing credentials with AI platforms

MITRE ATLAS Techniques

AML.T0049Exploit Public-Facing Application
AML.T0078Drive-by Compromise

Compliance Controls Affected

ISO 42001: A.6.2.6
NIST AI RMF: MANAGE 2.3
OWASP LLM Top 10: LLM03

What are the technical details?

Original Advisory

The HTML Forms – Simple WordPress Forms Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'arbitrary POST parameter NAME (the array key, not the value)' parameter in all versions up to, and including, 1.7.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Script execution does not require the Screen Options panel to be opened — injected attributes on the hidden-column checkboxes fire on page load as soon as the Submissions tab is rendered.

Exploitation Scenario

An attacker sends a crafted POST request to a public form built with HTML Forms, using a parameter name (the array key) that contains an HTML attribute-based payload. The plugin stores it without sanitization. When a site administrator opens the Submissions tab, the injected attributes on the hidden-column checkboxes run on page load, with no need to open Screen Options. The script uses the admin's session to create a rogue administrator account or install a backdoor plugin. From there the attacker can read data from the site and reach connected AI product backends or API keys stored in the site configuration.

Weaknesses (CWE)

CWE-79 — Improper Neutralization of Input During Web Page Generation: 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.

  • [Architecture and Design] Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.
  • [Implementation, Architecture and Design] Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies. For any data that will be output to another web page, especially any data that was received from external inputs, use the appropriate encoding on all non-alphanumeric characters. Parts of the same output document may require different encodings, which will vary depending on whether the output is in the: etc. Note that HTML Entity Encoding is only appropriate for the HTML body. Consult the XSS Prevention Cheat Sheet [REF-724] for more details on the types of encoding and escaping that are needed. HTML body Element attributes (such as src="XYZ") URIs JavaScript sections Casca

Source: MITRE CWE corpus.

CVSS Vector

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

Timeline

Published
November 18, 2026
Last Modified
November 18, 2026
First Seen
November 18, 2026

Related Vulnerabilities