CVE-2026-11777: Form Maker by 10Web SQL Injection Vulnerability
The Form Maker by 10Web WordPress plugin contains a SQL injection vulnerability in its 'name' parameter that allows authenticated administrators to execute arbitrary SQL queries. An attacker with admin access could extract sensitive database information by injecting malicious SQL code into form submissions. The vulnerability affects all versions up to and including 1.15.43.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 4.9 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
- Weaknesses (CWE)
- CWE-89
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-18 / 2026-06-18
NVD description (verbatim)
The Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder plugin for WordPress is vulnerable to generic SQL Injection via the 'name' parameter in all versions up to, and including, 1.15.43 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 administrator-level access, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
10 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-11777 is a SQL injection vulnerability (CWE-89) in Form Maker by 10Web versions ≤1.15.43. The plugin fails to properly escape user input in the 'name' parameter and does not use prepared statements, allowing authenticated high-privilege users to append arbitrary SQL commands to existing queries. The attack vector is network-based with low complexity, and while it requires administrator-level credentials, it provides confidentiality impact through unauthorized data extraction.
Business impact
Organizations running Form Maker on WordPress sites face potential exposure of sensitive database contents, including user data, email addresses, and other stored information accessible through the form's database tables. The risk is primarily to data confidentiality rather than availability or integrity. Since exploitation requires administrator credentials, the threat comes from insider actors or compromised admin accounts. The severity depends on the sensitivity of data stored in affected WordPress databases and integration with other business systems.
Affected systems
WordPress installations using the Form Maker by 10Web plugin in any version up to and including 1.15.43. The plugin is a drag-and-drop form builder used for creating contact forms and other interactive form elements. Any WordPress site with this plugin installed and an admin account is potentially at risk if that account is compromised or controlled by a malicious insider.
Exploitability
Exploitation requires authenticated access with administrator-level privileges, significantly limiting practical attack scenarios. An attacker cannot exploit this remotely without valid WordPress admin credentials. The attack is straightforward once privileged access exists—the 'name' parameter accepts injected SQL syntax due to insufficient input sanitization. The CVSS score of 4.9 (Medium) reflects the high privilege requirement offsetting the high confidentiality impact. This is not an unauthenticated, easy-to-exploit vulnerability, but represents a real risk in environments with compromised or untrusted admin accounts.
Remediation
Update the Form Maker by 10Web plugin to a patched version released after 1.15.43. Verify the exact patched version against the vendor's security advisory. Additionally, review WordPress administrator access controls—restrict admin roles to necessary personnel, enforce strong passwords, enable multi-factor authentication, and monitor admin activities for suspicious database queries or form modifications.
Patch guidance
Check the official 10Web plugin repository and security advisories for the released patch version. Update through WordPress's plugin management interface once a fix is available. Test the update in a staging environment to ensure form functionality remains intact. After patching, audit recent database activity logs if available to detect any malicious queries that may have been executed. Verify patch application by confirming the plugin version in WordPress settings matches the patched version.
Detection guidance
Monitor WordPress admin access logs for unusual login patterns or accounts. Examine WordPress database query logs (if enabled) for suspicious SQL syntax in the form_maker plugin operations, particularly queries containing UNION, SELECT FROM, or other injected SQL keywords appearing in the 'name' parameter. Use Web Application Firewalls (WAF) to detect SQL injection patterns. Review form submissions for abnormal 'name' field values containing SQL syntax. Consider using WordPress security plugins that log and alert on database query anomalies.
Why prioritize this
While the CVSS score is Medium (4.9), the vulnerability should be prioritized for patching due to its direct impact on database confidentiality and the potential for lateral movement once a database is compromised. Prioritize based on: (1) whether administrator accounts are well-protected with MFA, (2) the sensitivity of data stored in the WordPress database, and (3) whether the plugin actively receives form submissions. Organizations with strong admin access controls can defer patching slightly longer than those with weaker privilege management.
Risk score, explained
The CVSS 3.1 score of 4.9 reflects a Medium severity rating based on network accessibility (AV:N), low attack complexity (AC:L), and high privileges required (PR:H). The score emphasizes high confidentiality impact (C:H) but no integrity or availability impact. The privilege requirement significantly reduces the exploitability rating. Organizations should not dismiss this as low-risk; the ability to extract sensitive database contents is serious, but the admin-level prerequisite prevents widespread automated exploitation.
Frequently asked questions
Do I need to update immediately if I'm the only WordPress administrator and I trust myself?
Not necessarily if access controls are strong. However, best practice is to patch promptly regardless, since admin accounts can be compromised through phishing, malware, or weak password reuse. Delaying creates an ongoing risk window. Prioritize patching within your standard maintenance cycle.
Can an unauthenticated attacker exploit this vulnerability?
No. This vulnerability explicitly requires authenticated access with administrator-level privileges. Unauthenticated users cannot trigger the SQL injection. However, if an admin account is compromised through credential theft or social engineering, the vulnerability becomes exploitable.
What data is at risk?
Any data stored in the WordPress database accessible through SQL queries can potentially be extracted. This typically includes user accounts, email addresses, post content, plugin settings, and any custom database tables created by other plugins. The scope depends on the database user permissions assigned to WordPress.
Will my web application firewall (WAF) protect me?
A properly configured WAF with SQL injection detection rules should block many exploitation attempts by filtering malicious SQL syntax in the 'name' parameter. However, WAF rules can be bypassed with obfuscation. Patching remains the primary defense; WAF is a secondary layer.
This analysis is based on published vulnerability information as of the modification date provided. Readers should verify patch availability and version numbers directly with 10Web's official security advisories and the WordPress plugin repository. CVSS scores and severity ratings are provided as context for risk assessment and should not be used as the sole basis for remediation decisions. Organizations should assess this vulnerability within their own threat model, considering admin access controls, data sensitivity, and operational context. SEC.co and the author assume no liability for business decisions made based on this intelligence. Source: NVD (public-domain), retrieved 2026-07-27. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2026-0075MEDIUMAndroid SQL Injection in Contacts Database – Privilege Escalation Risk
- CVE-2026-10039MEDIUMFrontend Admin WordPress Plugin SQL Injection Vulnerability
- CVE-2026-10155MEDIUMSQL Injection in Bdtask Multi-Store Inventory Management System 1.0
- CVE-2026-10170MEDIUMSQL Injection in code-projects Visitor Management System 1.0
- CVE-2026-10171MEDIUMSQL Injection in code-projects Online Music Site 1.0 AdminUpdateAlbum.php
- CVE-2026-10176MEDIUMSQL Injection in Aider-AI Aider 0.86.3 Code Generation
- CVE-2026-10193MEDIUMSQL Injection in OFCMS ComnController – Authentication Required
- CVE-2026-10202MEDIUMOFCMS 1.1.3 SQL Injection in SystemDictController