CVE-2026-3359
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder plugin for WordPress is vulnerable to SQL Injection via the 'inputs' parameter in versions up to, and including, 1.15.42 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Form Maker plugin for WordPress versions up to 1.15.42 contains an unauthenticated SQL injection vulnerability in the 'inputs' parameter. The plugin fails to properly escape user input and lacks prepared statements in the SQL query, allowing attackers to inject arbitrary SQL commands to extract sensitive data from the database.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Form Maker plugin installationIn WordPress admin, go to Plugins > Installed Plugins and locate Form Maker, or check the plugin files for version information in the plugin header commentAffected if Form Maker plugin is installed and active
-
Check installed version against affected rangeRead the version number from the plugin metadata (typically displayed in the WordPress plugins list or in the main plugin PHP file header)Affected if The installed version is 1.15.42 or any earlier version (up to and including 1.15.42)
-
Confirm plugin is accessible without authenticationVerify the WordPress site is publicly accessible and the Form Maker plugin functionality (form submission endpoints) can be reached without logging inAffected if The site and plugin endpoints are reachable without authentication (this is the default and expected configuration)
The environment is affected if the Form Maker plugin version is 1.15.42 or earlier and the plugin is active and accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the Form Maker plugin to the latest version immediately. If no patched version is available, disable the plugin or implement web application firewall rules to block malicious 'inputs' parameter requests.
Latest available version of Form Maker by 10Web plugin (version higher than 1.15.42)
- Check the current version of the Form Maker by 10Web plugin installed on your WordPress site
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Locate Form Maker by 10Web and note the current version number
- If the installed version is 1.15.42 or below, update the plugin to the latest available version
- After updating, verify the plugin is functioning correctly by submitting a test form
- Review the plugin changelog to confirm the security fix for the SQL injection vulnerability is included
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3359 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3359 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data