CVE-2026-118067 · Package
NO FIX YET · SEE WHAT TO DO
The Form Maker by 10Web WordPress plugin, in all versions up to and including 1.15.50, fails to sanitize form input and escape output. An unauthenticated attacker can store scripts that run in a site administrator's browser when they open the form's Submissions page, if the form contains a File Upload field.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Form Maker by 10Web plugin version 1.15.50 or earlier, especially forms that include a File Upload field. The attacker needs no account, and an administrator must open the Submissions page of the affected form for the script to run. Sites without this plugin or with no File Upload forms are not affected.
Not affected if no-file-upload-field, plugin-not-installed, plugin-updated-past-1.15.50
Who cares form-maker, self-hosted, wordpress, wordpress-plugin
wp-content/plugins/ for the plugin folder.1.15.50; the exact fixed version is unknown from the sources.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.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.