dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-1065

HIGH · 7.2 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
The Form Maker by 10Web plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 1.15.35. This is due to the plugin's default file upload allowlist including SVG files combined with weak substring-based extension validation. This makes it possible for unauthenticated attackers to upload malicious SVG files containing JavaScript code that will execute when viewed by administrators or site visitors via file upload fields in forms granted they can submit forms.

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

The Form Maker by 10Web plugin for WordPress allows file uploads through form fields with SVG files enabled by default in the allowlist. The extension validation uses weak substring matching that can be bypassed, enabling unauthenticated attackers to upload malicious SVG files containing JavaScript payloads. When administrators or site visitors view these uploaded files, the embedded JavaScript executes, leading to stored XSS.

MitigationDisable SVG file uploads in the plugin settings or implement strict MIME type validation and server-side file content analysis to block malicious SVG uploads until a patched version is available.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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 checks

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

  1. Verify Form Maker by 10Web plugin is installed
    Navigate to WordPress admin > Plugins and confirm Form Maker by 10Web is active
    Affected if Plugin is installed and active in WordPress
  2. Check the installed plugin version
    In WordPress admin > Plugins > Form Maker by 10Web > View Details, note the version number and compare against any official vulnerability advisory
    Affected if Version is unknown, unpatched, or within an affected range
  3. Confirm SVG file uploads are enabled in plugin settings
    Go to Form Maker > Settings > General > File Upload Options and check if SVG appears in the allowed extensions or allowlist
    Affected if SVG extension is present in the allowed file types list
  4. Inspect uploaded SVG files for malicious content
    Examine files in wp-content/uploads/form-maker/ (or similar upload directories used by the plugin) and review SVG files for embedded <script> tags, onload, onerror, or other JavaScript event handlers
    Affected if SVG files containing executable JavaScript are present in upload directories
  5. Review form configurations for file upload fields
    In Form Maker > Manager > select each form > Edit Form > Fields, identify any file upload fields and verify their allowed extensions settings
    Affected if Any file upload field allows SVG file type

A user is affected if the Form Maker by 10Web plugin is active with SVG uploads enabled in settings and malicious SVG files exist in the upload directory, allowing stored XSS execution.

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

Disable SVG file uploads in the plugin settings or implement strict MIME type validation and server-side file content analysis to block malicious SVG uploads until a patched version is available.

Recommended fix Moderate confidence

Latest version after 1.15.35 (check wordpress.org for current release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Form Maker by 10Web' plugin
  4. Check the current version number (ensure it is 1.15.35 or below)
  5. If an update is available, click 'Update Now' to install the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/form-maker and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the version in Plugins > Installed Plugins
  8. Review form configurations to ensure file upload fields have proper file type restrictions if needed

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1065 — 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-1065 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