dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-39502

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Unauthenticated SQL Injection in Form Maker by 10Web <= 1.15.38 versions.

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 confidence

Unauthenticated SQL Injection vulnerability in Form Maker by 10Web plugin for WordPress allows remote attackers to inject malicious SQL queries via unsanitized input in plugin parameters, potentially leading to data exfiltration or complete database compromise.

MitigationUpdate Form Maker by 10Web plugin to the latest version beyond 1.15.38 which contains the patched code; alternatively, disable the plugin until patched.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Form Maker by 10Web plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Form Maker by 10Web' in the list, or inspect the file /wp-content/plugins/form-maker/ for existence
    Affected if Plugin is not present on the system
  2. Check if the plugin is active
    In WordPress admin > Plugins, verify that Form Maker by 10Web shows as 'Active'
    Affected if Plugin is active and exposed to the web
  3. Identify the installed version number
    In WordPress admin > Plugins > Form Maker by 10Web, click on 'View Details' to display the version number, or read the version from the plugin header in /wp-content/plugins/form-maker/form-maker.php
    Affected if Version is at or below 1.15.38
  4. Verify plugin is accessible to unauthenticated users
    Confirm the WordPress site allows public access and the Form Maker plugin endpoints are reachable without authentication (the SQLi is unauthenticated, so any public-facing form submission page could be targeted)
    Affected if Plugin is active and site is publicly accessible

You are affected if Form Maker by 10Web plugin is installed, active, accessible to unauthenticated users, and the installed version is 1.15.38 or lower.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Form Maker by 10Web plugin to the latest version beyond 1.15.38 which contains the patched code; alternatively, disable the plugin until patched.

Recommended fix High confidence

Upgrade to the latest version of Form Maker by 10Web (any version above 1.15.38)

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Locate 'Form Maker by 10Web' in the plugin list
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest patched version
  5. 5. Verify the plugin updated successfully to a version higher than 1.15.38
  6. 6. Test form submissions to ensure the plugin functions correctly after update
Caveat Review plugin settings after upgrade as minor configuration changes may occur between versions

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39502 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39502 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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