CVE-2026-109214 json
User Frontend <= 4.3.13 - Unauthenticated Stored Cross-Site Scripting via Taxonomy Field Text-Input
published 4d ago modified 4d ago also EUVD-2026-119162
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
The User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '<taxonomy_field_name> (default: 'category')' parameter in all versions up to, and including, 4.3.13 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. Exploitation requires the target installation to have configured a Taxonomy field in text-input mode with guest post submission enabled on at least one frontend form.
Is CVE-2026-109214 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4d ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- wedevs User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/ca1837a4-ea04-4a82-aadb-43e9cff28833?source=cve
- plugins.trac.wordpress.org /browser/wp-user-frontend/tags/4.3.13/admin/form-builder/views/post-form-settings.php#L498
- plugins.trac.wordpress.org /browser/wp-user-frontend/tags/4.3.13/admin/html/form-settings-post.php#L118
- plugins.trac.wordpress.org /browser/wp-user-frontend/tags/4.3.13/includes/Traits/FieldableTrait.php#L745
- plugins.trac.wordpress.org /browser/wp-user-frontend/tags/4.3.13/includes/Ajax/Frontend_Form_Ajax.php#L36
- plugins.trac.wordpress.org /browser/wp-user-frontend/tags/4.3.13/includes/Ajax.php#L26
- plugins.trac.wordpress.org /browser/wp-user-frontend/tags/4.3.13/admin/form-builder/assets/js/form-builder.js#L666
- plugins.trac.wordpress.org /changeset?reponame=&new=3770255%40wp-user-frontend%2Ftags%2F4.3.14&old=3722911%40wp-user-frontend%2Ftags%2F4.
Sources
- CVE List CVE-2026-109214
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.