Pie Register Premium ≤ 3.8.4.0: The Upload Validation That Ran — and Was Never Checked (CVE-2026-84999, 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 →

Pie Register Premium ≤ 3.8.4.0: The Upload Validation That Ran — and Was Never Checked (CVE-2026-84999, CVSS 9.8)

The plugin did validate the file type. It called the right WordPress functions — wp_check_filetype() and wp_check_filetype_and_ext() — and then saved the file without ever looking at the answer. CVE-2026-84999 is what that missing glance costs: an unauthenticated visitor can upload a PHP file through Pie Register Premium's registration form, the response hands back the exact filename it was saved under, and requesting that file runs it. No account, no interaction — remote code execution at CVSS 9.8.

What Happened

CVE-2026-84999 is an unrestricted file upload vulnerability (CWE-434, upload of a file with a dangerous type) in Pie Register Premium, the paid user-registration plugin by Genetech Solutions, disclosed October 27, 2026 (CNA: Wordfence).

Am I Affected?

This is the Premium plugin, and the distinction matters: check wp-admin → Plugins for "Pie Register Premium" and its version. At 3.8.4.0 or below, you are in the affected range.

Do not confuse it with the free Pie Register plugin on wordpress.org. The free plugin shares the 3.8.4.x version numbers but is a different distribution, and its public changelog is already past this range — a "you're up to date" reading from the free plugin says nothing about a Premium install on the same site.

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 directory slug for the Premium plugin, and keying a check to the free plugin's slug would produce wrong claims in both directions. 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 Pie Register Premium today — or, if registration cannot stop, disable its file-upload fields. With no patch available, removing the upload path is the fix you have.
  2. Check your uploads directory for PHP files that should not be there. An uploaded script only matters once it is requested, and it may already be sitting in wp-content/uploads (or the plugin's upload folder) waiting. Any .php file there that you cannot explain is a finding, not a curiosity.
  3. Audit administrator accounts. Users → All Users: every Administrator should be a person you can name. Upload-to-RCE ends at full site control; the account audit is how you learn whether anyone already walked through.
  4. Watch the vendor for a fixed release — and do not treat an update that does not mention CVE-2026-84999 as a fix for CVE-2026-84999.

The Bigger Lesson

Registration forms are unauthenticated attack surface by design — they exist for strangers — and every field on them, especially file uploads, needs its validation result actually enforced. Calling the validator is not validating. This is the same class as the Bricksforge flaw (CVE-2026-85097) in a different plugin: the check existed, the enforcement didn't, and the gap between those two things is where the shell lands. When an AI builder wires up a registration form for you, "does it validate uploads?" is the wrong question — the right one is "show me where the code refuses the file when validation fails."

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 uploads audit finds a stranger.


Running a registration plugin? 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