Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessScrape nonce from public form page
-
DeliverySend crafted request to form handler
-
ExploitInject SQL via 'inputs' parameter
-
ExecutionBlind boolean/time-based extraction
-
ImpactExfiltrate credentials and secrets
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target site have the 10Web Form Maker plugin (version ≤1.15.48) installed and at least one of its forms rendered on a publicly accessible page - this is the realistic default usage of a contact-form plugin. The only procedural prerequisite, a valid nonce reaching the vulnerable handler, is not a meaningful barrier because the description confirms the nonce is emitted to every public page that renders a form, making it obtainable from page source without authentication. There is no required user interaction, no authentication, and no non-default configuration needed; the practical limiting factor is simply that a Form Maker form must be publicly exposed on the site. |
| Impact | This is a genuinely high-priority issue, not an inflated-CVSS artifact. All available signals align: the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes network-reachable, low-complexity exploitation requiring no authentication, and the description reinforces this by noting the nonce guarding the vulnerable handler is emitted into the public page source of any page rendering a form - so the one apparent gating factor (nonce validation) is trivially defeated by an unauthenticated attacker, justifying AC:L rather than AC:H. The impact is scoped to confidentiality only (C:H/I:N/A:N), consistent with a blind SQL injection used to exfiltrate database contents (WordPress user hashes, secrets) rather than modify data or crash the service. No EPSS score was supplied, there is no CISA KEV listing, and no public proof-of-concept is referenced, so real-world exploitation volume cannot be quantified from the input - the risk rating here is driven by exploitability characteristics and the low barrier to weaponization of an unauthenticated SQLi in a WordPress plugin, a class historically targeted by automated mass-scanning once details are public. No signals conflict; the main missing data is EPSS and any exploitation telemetry. |
| Exploit ScenarioDerived | An unauthenticated attacker visits any public page of the target site that renders a 10Web Form Maker form, scrapes the exposed nonce from the page source, and submits a crafted request to the vulnerable form handler with SQL payloads in the 'inputs' parameter. Because the query is neither escaped nor prepared, the injected clauses execute blind against the database, letting the attacker iteratively extract sensitive data such as WordPress administrator password hashes. No public exploit code is identified at time of analysis, but the technique is straightforward to automate. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Blind SQL injection in the 10Web Form Maker WordPress plugin (all versions up to and including 1.15.48) lets unauthenticated remote attackers append additional SQL to queries built from the 'inputs' parameter, allowing them to extract sensitive information from the site's database. The plugin's nonce check offers no real protection because the required nonce is emitted into the HTML source of every public page that renders a form, so the only practical prerequisite is that a Form Maker form be reachable by an anonymous visitor - the normal way a contact-form plugin is deployed. CVSS is 7.5 (AV:N/AC:L/PR:N/UI:N, confidentiality-only), no public exploit code has been identified at time of analysis, and the issue should still be treated as high priority given how trivially the vulnerable handler can be reached.
RemediationAI
Update the Form Maker by 10Web plugin to a release newer than 1.15.48 as soon as possible; the fix is already in the plugin's source history via the WordPress.org changeset referenced in the advisory (https://plugins.trac.wordpress.org/changeset?reponame=&old=3730401%40form-maker&new=3730401%40form-maker), so an upstream fix is available (commit/changeset); a released patched version number is not independently confirmed from the data provided, so verify the installed version after updating and consult the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/d51a8673-8fe0-4329-970d-085db5cdf2d3?source=cve) for the vendor's stated fixed release. If updating immediately is not possible, the most effective compensating control is to deactivate the plugin until it can be patched, at the cost of losing all published forms; a less disruptive option is to unpublish or password-protect every page that renders a Form Maker form, which removes the nonce and the reachable handler but degrades site functionality, or to front the site with a WAF rule that rejects SQL metacharacters and known injection patterns in requests carrying the 'inputs' parameter, accepting that rule evasion and false positives on legitimate submissions are possible and that a WAF is only a temporary stopgap. Because exploitation requires no authentication, no user interaction and no non-default configuration, exposure should be treated as continuous until the patch is applied.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a classic CWE-89 SQL injection in a WordPress plugin written in PHP. User-supplied form input delivered through the 'inputs' parameter is concatenated into an existing SQL statement without adequate escaping and without use of prepared statements/parameter binding, so attacker-controlled fragments are executed as part of the query. The sink is reached through the plugin's frontend controller (frontend/controllers/form_maker.php) and the shared query-building helpers in framework/WDW_FM_Library.php (referenced lines 366, 6274 and 6809), with additional call paths in the main plugin bootstrap form-maker.php (lines 931 and 1229); because the injection is blind, extraction proceeds by inference (boolean- or time-based) rather than by direct result output, which raises the skill/effort bar slightly but not the exposure. A nonce is required to hit the vulnerable handler, yet it is rendered into every public page containing a Form Maker form, so it functions as a CSRF token rather than an access control and is trivially harvested from page source by an unauthenticated attacker. The affected component is identified by the CPE cpe:2.3:a:10web:form_maker_by_10web_-_mobile-friendly_drag_&_drop_contact_form_builder:*:*:*:*:*:*:*:*, covering the whole plugin line up to and including 1.15.48.
Know when Form Maker By 10Web Mobile Friendly Drag Drop Contact Form Builder gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Remote, no auth (nonce is public), low complexity; blind SQLi yields high confidentiality impact but no integrity or availability change, scope unchanged.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Form Maker by 10Web - Mobile-Friendly Drag & Drop Contact Form Builder plugin for WordPress is vulnerable to blind SQL Injection via the 'inputs' parameter in all versions up to, and including, 1.15.48 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The nonce required to reach the vulnerable handler is emitted to every public page that renders a form, making it trivially obtainable by an unauthenticated attacker from page source.
Executive ViewAI
10Web Form Maker, a WordPress plugin used to publish public contact and submission forms, is affected by a blind SQL injection that any anonymous visitor can trigger on sites running versions up to and including 1.15.48. Because the plugin is normally deployed on publicly reachable pages and no vendor patch is available, any organization hosting an affected form should assume its WordPress database - including user credentials and any customer data stored alongside it - is exposed to an outside attacker without login or specialized tooling. Leadership should treat this as a priority remediation item because the resulting data exposure would likely trigger breach-notification, privacy, and contractual obligations.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate the 10Web Form Maker plugin or unpublish all publicly reachable forms where business use permits; otherwise restrict the form-submission endpoint to authenticated or allowlisted sources; apply WAF or reverse-proxy virtual patching rules blocking SQL injection patterns (quote characters, UNION, boolean/stacked-query constructs) on the plugin endpoint; reduce the WordPress database account to least privilege; enable and monitor web, WAF, and database audit logs for anomalous queries from the plugin handler; and conduct a database integrity and account review for signs of prior extraction.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
Unauthenticated SQL injection in Form Maker by 10Web plugin allows remote attackers to extract sensitive database conten
Stored cross-site scripting in the 10Web Form Maker WordPress plugin through version 1.15.47 lets unauthenticated attack
Stored Cross-Site Scripting in Form Maker by 10Web WordPress plugin (versions ≤1.15.40) allows unauthenticated attackers
Reflected cross-site scripting (XSS) in the Form Maker by 10Web WordPress plugin (versions up to and including 1.15.48)
Reflected XSS in the Form Maker by 10Web WordPress plugin (all versions ≤1.15.46) allows unauthenticated attackers to in
Blind SQL injection in the Form Maker by 10Web WordPress plugin exposes full database read access to authenticated subsc
SQL injection in the Form Maker by 10Web WordPress plugin exposes the WordPress database to authenticated admin-level at
SQL Injection in the Form Maker by 10Web WordPress plugin (all versions up to and including 1.15.43) enables authenticat
SQL injection in Form Maker by 10Web WordPress plugin (versions ≤1.15.40) allows authenticated administrators to extract
EUVD-2026-100797
GHSA-6f5c-93fp-5pqh
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB