CVE-2026-15993: Form Maker by 10Web (WordPress plugin) · SQL Injection
Affects Form Maker by 10Web (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| 10webForm Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder | Affected
| Fixed in– |
AI-suggested
Until a patch is available, consider restricting subscriber-level access or disabling the use of DB-backed dynamic choice fields referencing the {username} placeholder. Monitor vendor communications for updates and apply official patches once released.
Description
The Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder plugin for WordPress is vulnerable to blind SQL Injection via '{username}' Placeholder in Dynamic-Choice Field WHERE Clause in all versions up to, and including, 1.15.44 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This requires that a form is configured with a DB-backed dynamic choice field whose WHERE template references the {username} placeholder, and the attacker must first set their own display_name to a SQL payload via the standard WordPress profile edit screen before triggering the fm_reload_input AJAX endpoint.
References
- wordfence.com/threat-intel/vulnerabilities/id/1665bf5a-3bf0-4907-a7df-a2fe26f11869?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/form-maker/tags/1.15.44/framework/WDW_FM_Library.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/form-maker/tags/1.15.44/frontend/views/form_maker.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/form-maker/tags/1.15.44/framework/WDW_FM_Library.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/form-maker/tags/1.15.44/frontend/controllers/form_maker.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/form-maker/tags/1.15.43/framework/WDW_FM_Library.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/form-maker/tags/1.15.43/frontend/views/form_maker.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/form-maker/tags/1.15.43/framework/WDW_FM_Library.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/form-maker/tags/1.15.43/frontend/controllers/form_maker.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3632835%40form-maker&new=3632835%40form-maker (opens in a new tab)