SimpleForm ≤ 3.10.2: One Trailing Dot Walks Past Every Upload Check (CVE-2026-118235, CVSS 9.8)

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

SimpleForm ≤ 3.10.2: One Trailing Dot Walks Past Every Upload Check (CVE-2026-118235, CVSS 9.8)

The extension check ran. The MIME check ran. And the file got through anyway — because the code decided what the file was before it cleaned up what the file was called, and a filename ending in a single dot was enough to walk the real extension past both checks. In SimpleForm – Form Maker to Chat Apps with Quiz, Poll and Multi Lead Notifications at version 3.10.2 and below, that ordering bug is CVE-2026-118235: an unauthenticated arbitrary file upload where, in the CVE record's words, uploaded files "may be executable, which makes remote code execution possible." It scores CVSS 9.8 — and the CVE record names no patched version yet.

What Happened

CVE-2026-118235 is an unauthenticated arbitrary file upload vulnerability in the SimpleForm plugin for WordPress, disclosed October 31, 2026 (CNA: Wordfence).

Am I Affected?

Check wp-admin → Plugins for SimpleForm and its version. At 3.10.2 or below, with a public form on the site, you are in the affected range: the nonce that gates the upload path is sitting in that form's markup for anyone to copy.

One honesty note, because it is the whole point of how we cover these: our scanner does not claim a version check for this one. The CVE record names no wordpress.org listing for this plugin, and no listing was verified — so no slug is asserted and no install count is quoted here. Keying a readme check to a guessed slug would produce claims we cannot stand behind in either direction. This article exists because the flaw is real and urgent — not because we can detect it passively. What the free mini-scan can do is check the rest of your site's exposed surface while you handle this one by hand.

What To Do Now

  1. Disable file-upload fields — or the plugin — until the vendor ships a release naming this CVE. There is no patched version to update to yet. A form that cannot accept files cannot be used to upload one.
  2. Check the uploads directory for files that should not be there. Form uploads should be the documents and images your forms were built to collect. Anything executable-shaped, or anything you cannot tie to a real submission, is a stranger until proven otherwise.
  3. Audit administrator accounts. Users → All Users: every Administrator should be a person you can name. An unauthenticated upload flaw is exactly the kind that gets quietly converted into a persistent admin account.
  4. When a fix does ship, update and confirm it names CVE-2026-118235. An update that does not mention this CVE is not evidence this CVE is fixed.

The Bigger Lesson

Validation order is not an implementation detail — here, it is the vulnerability. Deriving a file's type from an unsanitized name means the attacker chooses the input to your security decision, punctuation included; sanitizing afterward only cleans the name of the file you already waved through. And a nonce rendered into public markup is not access control, however official it looks in the code — a gate key that ships with the page turns no one away. If your forms accept files, the questions worth asking today are which server-side allowlist decides what may arrive, and whether anything about that decision trusts the name the visitor gave it.

Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the audit finds a stranger.


Running SimpleForm at 3.10.2 or below? Take the upload fields off until a patched release names this CVE, then run the free check at preshipit.com/free-scan — it covers the exposures a scan can see, and articles like this one cover the ones it can't.

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report