WordPress security changelog
HIGH CVE-2026-19806 Deferred

Support Genix permits Subscriber-level administrator account takeover

Support Genix through 1.4.52 derives its site-wide AES-256-CBC key from three two-digit random values and an activation timestamp, leaving about 729,000 key candidates. A Subscriber who obtains one legitimate guest-ticket token and can bound the activation time can recover the key offline, forge a token for an administrator-owned ticket, and submit it through /sgnix/?p=. guest_ticket_login() then calls wp_set_auth_cookie() for that administrator without a capability, nonce, or session check.

CVE / CNA score 8.8 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Support Genix – Helpdesk, AI Chatbot, Knowledge Base & Customer Support Ticketing System
Plugin slug
support-genix-lite
Affected
<= 1.4.52
Safe version
See mitigation notes
Published
Sep 01, 2026
Weakness
CWE-287 — Improper Authentication

This CVE was published Sep 01, 2026 and is one of 4 known issues for this plugin.

What to do

Update, patch or deactivate.

Update to a confirmed release newer than 1.4.52 when available. Until then, disable guest ticket login when warranted, invalidate active sessions, and audit administrator accounts, ticket access, and authentication activity.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The Support Genix – Helpdesk, AI Chatbot, Knowledge Base & Customer Support Ticketing System plugin for WordPress is vulnerable to Authentication Bypass leading to Administrator Account Takeover in all versions up to, and including, 1.4.52 via the `guest_ticket_login()` function and its `p` parameter. This is due to the site-wide AES-256-CBC encryption key being derived from only three two-digit `wp_rand(10, 99)` values and a Unix timestamp via `md5()` — yielding approximately 19.5 bits of entropy — combined with a deterministic IV derived from the password, no authentication tag on the ciphertext, and no capability check, nonce, or session validation on the publicly reachable `/sgnix/?p=<token>` endpoint. This makes it possible for authenticated attackers, with subscriber-level access and above, who can obtain a single legitimate guest ticket token as a known-plaintext oracle and bound the plugin activation timestamp, to exhaust the ~729,000-candidate keyspace entirely offline, recover the site-wide encryption key, and forge a self-consistent `{ticket_id, ticket_user}` token targeting any administrator-owned ticket. Submitting the forged token to the unprotected endpoint causes `wp_set_auth_cookie()` to be called for that administrator, granting the attacker full administrative access to the WordPress site.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References

Primary and upstream sources