CVE-2026-120512 · Package
NO FIX YET
The Form Maker by 10Web WordPress plugin, in versions up to and including 1.15.50, does not sanitize a hidden form field's name, so an unauthenticated attacker can store a script in a form submission. When an administrator clicks Show-on-Map on that submission, the script runs in the administrator's session.
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 at or below 1.15.50 are exposed, because stored form data is rendered unescaped in the admin Submissions view. Exploitation needs an administrator to open a submission and click Show-on-Map, so sites with no such plugin installed can skip it.
Not affected if plugin-not-installed
Who cares 10web, form-maker, wordpress
1.15.50 are affected.No fix yet, per 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_<n>_element<id> (Hidden Input field, name = user-defined, e.g. hidden_probe)' 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. Exploitation requires an administrator to open the Submissions screen and click the Show-on-Map link associated with the poisoned entry, at which point the attacker-controlled field_id value is echoed unescaped into a single-quoted JavaScript string in the FormMakerEditCountryinPopup popup — a step whose nonce and capability checks are automatically satisfied by the administrator's own session and the freshly minted fm_ajax_nonce embedded in the link.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/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.