Running JetFormBuilder on your site? Check it against CVE-2026-119481 — free.
The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your JetFormBuilder is in the affected range (≤ 3.6.7.1), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.
Run the free mini-scan →A form builder's job is taking input from strangers — and when its privilege assignment is wrong, the stranger's input can come with administrator rights attached. CVE-2026-119481, an unauthenticated privilege escalation flaw in the JetFormBuilder WordPress plugin at version 3.6.7.1 and below, carries a CVSS score of 9.8. The fix exists and is already the version wordpress.org serves: 3.6.8. This is a pure update-discipline problem.
CVE-2026-119481 is an incorrect privilege assignment vulnerability (CWE-266) in JetFormBuilder (vendor: Crocoblock), disclosed November 4, 2026 (CNA: Patchstack). The plugin sits on 80,000+ sites.
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Network-reachable, low complexity, and PR:N: no privileges are required at all. Patchstack lists the required privilege as "Unauthenticated."Check wp-admin → Plugins for JetFormBuilder and its version. At 3.6.7.1 or below, you are in the affected range.
This one is version-checkable, and our scanner checks it: the free mini-scan reads the plugin's public readme and flags a stable tag at or below 3.6.7.1 as a High finding naming CVE-2026-119481. A site on 3.6.8 or later earns the opposite note — it is at or above the verified patched release. The check reads the version only; it never submits a form, registers an account, or attempts a role change, because there is no passive version of that test.
Privilege assignment is a security decision made in code defaults. A plugin author writing "give this submission the default role" is deciding, for every site that installs the plugin, how much trust a stranger's form submission carries. When that decision is wrong, the failure mode is silent: no crash, no warning — just an account that should not exist, created by someone who never had one. The defence is boring and complete: keep the plugins that touch identity on a short update leash, and audit the user list on a schedule, not on a suspicion.
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 step finds a stranger's work.
Running JetFormBuilder? Update to 3.6.8, then run the free check at preshipit.com/free-scan — it flags JetFormBuilder ≤ 3.6.7.1 and the rest of your site's exposed surface in about a minute.
Check JetFormBuilder on your own site — free.
Our free WordPress Plugin Vulnerability Checker pulls JetFormBuilder's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-119481 included. No scan, no account.
Open the free plugin checker →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.
Running JetFormBuilder on your site? Check it against CVE-2026-119481 — free.
The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your JetFormBuilder is in the affected range (≤ 3.6.7.1), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. 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