CVE-2026-1065

Form Maker by 10Web <= 1.15.35 - Unauthenticated Stored Cross-Site Scripting via SVG file

Strategic Overview

Status
Patched in 1.15.36
Affected Version
<= 1.15.35
CVSS
7.2High
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2026-1065
View all Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder vulnerabilities

At a glance

CVE-2026-1065 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Form Maker by 10Web WordPress plugin, affecting versions <= 1.15.35. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.15.36; sites on affected versions should update now. Disclosed February 2026, reported by Supakiad S. (m3ez) (m3ez).

Vulnerability Overview

The Form Maker by 10Web plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 1.15.35. This is due to the plugin's default file upload allowlist including SVG files combined with weak substring-based extension validation. This makes it possible for unauthenticated attackers to upload malicious SVG files containing JavaScript code that will execute when viewed by administrators or site visitors via file upload fields in forms granted they can submit forms.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-434: Unrestricted Upload of File with Dangerous Type

Reaching this weakness in Form Maker by 10Web <= 1.15.35 takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For Form Maker by 10Web the fix is 1.15.36: builds <= 1.15.35 are affected, anything from 1.15.36 onward is not.

Remediation

Update to version 1.15.36, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Form Maker by 10Web 1.15.36 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C