CVE-2026-118067 json
Form Maker by 10Web <= 1.15.50 - Unauthenticated Stored Cross-Site Scripting via disabled_fields Parameter
published 3d ago modified 2d ago also EUVD-2026-118565
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
The Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'wdform_<field_id>_element<form_id> (payload) + disabled_fields<form_id> (pivot)' parameter in all versions up to, and including, 1.15.50 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. This requires the targeted form to contain a File Upload field, as the attacker must suppress that field's storage row via the disabled_fields parameter to shift a controlled text-field value into the positional slot where escaping is skipped; execution occurs when an administrator opens the Submissions page for the affected form.
Is CVE-2026-118067 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
- 2d ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- 10web Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/abc75a73-f515-42eb-ad4a-79e8900057c0?source=cve
- plugins.trac.wordpress.org /browser/form-maker/tags/1.15.50/admin/models/Submissions_fm.php#L707
- plugins.trac.wordpress.org /browser/form-maker/tags/1.15.50/admin/views/Submissions_fm.php#L620
- plugins.trac.wordpress.org /browser/form-maker/tags/1.15.50/admin/views/Submissions_fm.php#L658
- plugins.trac.wordpress.org /browser/form-maker/tags/1.15.50/frontend/models/form_maker.php#L2633
- plugins.trac.wordpress.org /browser/form-maker/tags/1.15.50/frontend/models/form_maker.php#L1637
- plugins.trac.wordpress.org /browser/form-maker/tags/1.15.50/frontend/models/form_maker.php#L1549
- plugins.trac.wordpress.org /browser/form-maker/tags/1.15.50/form-maker.php#L182
- plugins.trac.wordpress.org /browser/form-maker/tags/1.15.51
Sources
- CVE List CVE-2026-118067
- NVD CVE-2026-118067
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.