Running ELEX WordPress HelpDesk on your site? Check it against CVE-2026-114630 and CVE-2026-119077 — free.
The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your ELEX WordPress HelpDesk is in one of the affected ranges above, 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 support form's nonce is printed for every visitor — it was never an access control. In the ELEX WordPress HelpDesk & Customer Ticketing System plugin, that public nonce is the only guard on a deserialization that trusts everything arriving with it. That is CVE-2026-119077, scoring CVSS 9.8, disclosed November 13, 2026 (CNA: Wordfence).
CVE-2026-119077 is an unauthenticated PHP object injection vulnerability in the ELEX WordPress HelpDesk plugin (wordpress.org slug elex-helpdesk-customer-support-ticket-system, 200+ active installs on the directory listing at disclosure time — and still 200+, with current version 3.4.0, when this article shipped).
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Network-reachable, low complexity, no privileges and no user interaction required.ticket_label field inside the url-encoded form parameter with no server-side authentication and no class allowlist. The only guard is a nonce publicly emitted on any page carrying the [wsdesk_support] shortcode: one anonymous visit harvests the wsdesk_nonce, and one unauthenticated POST after it can execute code on the server.[wsdesk_support] support form must exist — which is the plugin's normal deployment. A version read alone proves neither the form's presence nor the exposure.Check wp-admin → Plugins for ELEX WordPress HelpDesk and its version. At 3.3.9 or below, with the public [wsdesk_support] support form published, your site runs the affected code.
Our scanner checks it: run the free mini-scan, or check just this plugin at /tools/plugin-check?slug=elex-helpdesk-customer-support-ticket-system. The check reads the version your site announces and flags anything at or below 3.3.9. Because the CVE record names no fixed version, a version above the range earns no "patched" claim from us — the check stays silent rather than guessing. The check never submits a ticket or a form — it reads the public version disclosure only.
A nonce is a CSRF token for logged-in flows, not an authentication barrier. Anything deserialized on the strength of a public nonce is unauthenticated input, and unserializing unauthenticated input without a class allowlist hands the caller a code-execution primitive. If a value is printed for every visitor, it authenticates no one.
Related: ELEX HelpDesk ≤ 3.3.8: file deletion through the public support form (CVE-2026-114630) — the sibling flaw in the same plugin. WordPress Hardening for AI-Built Sites — the standing version of this discipline.
Running ELEX WordPress HelpDesk for support tickets? Update to the newest release today, audit your administrator accounts, then run the free check at preshipit.com/free-scan — our scanner checks it, version-checking this plugin against CVE-2026-119077 from the version your site announces to the world.
Check ELEX WordPress HelpDesk on your own site — free.
Our free WordPress Plugin Vulnerability Checker pulls ELEX WordPress HelpDesk's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-114630 and CVE-2026-119077 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 ELEX WordPress HelpDesk on your site? Check it against CVE-2026-114630 and CVE-2026-119077 — free.
The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your ELEX WordPress HelpDesk is in one of the affected ranges above, 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