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 →A contact form is supposed to accept a name, an email address, maybe a résumé. In WP Libre Form at version 1.5.0.1, a form submission accepts something else as well: a PHP file, uploaded by a visitor with no account, saved to a web-accessible location, ready to be executed. That is CVE-2026-118423, an unauthenticated arbitrary file upload leading to remote code execution, scoring a perfect CVSS 10.0 — and the CVE record names no patched version yet.
CVE-2026-118423 is an unauthenticated remote code execution vulnerability in the WP Libre Form plugin for WordPress, disclosed November 6, 2026 (CNA: WPScan).
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. Network-reachable, low complexity, no privileges, no user interaction, and a changed scope: the vulnerable component is the plugin, but the impact lands on the whole server it runs on.Check wp-admin → Plugins for a plugin named WP Libre Form and its version. At 1.5.0.1, you are in the affected range — and the exposed surface is any public form on the site that accepts a file.
Two honesty notes, because they are the whole point of how we cover these. First: the CVE record names no wordpress.org directory slug for this plugin, and the one candidate listing carries no readable version or install data — so no install count is quoted here, and we will not guess at how many sites run it. Second: our scanner does not claim a version check for this one. With no verified slug and no readable version disclosure, 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.
.php file there is a stranger until proven otherwise.Any form that accepts files is an upload endpoint with admin-level consequences. The validation that matters is not the file extension a browser suggests or a MIME type a client declares — it is a server-side decision about what the file actually is and where it is allowed to live, made before the file reaches a place the web server will execute. A form builder that skips that decision has not shipped a convenience feature; it has shipped a shell with a contact form drawn on it. If your site takes uploads anywhere — forms, applications, portfolios — the question worth asking today is which code, exactly, decides what a stranger's file is allowed to become.
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 WP Libre Form 1.5.0.1? Disable it 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