ELEX WordPress HelpDesk & Customer Ticketing System <= 3.3.5 - Missing Authorization
Strategic Overview
- Status
- Patched in 3.3.6
- Affected Plugin
- ELEX WordPress HelpDesk & Customer Ticketing System
- Affected Version
<= 3.3.5- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-68837
At a glance
CVE-2025-68837 is a medium-severity Missing Authorization vulnerability in the ELEX WordPress HelpDesk & Customer Ticketing System WordPress plugin, affecting versions <= 3.3.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.3.6; sites on affected versions should update now. Disclosed January 2026, reported by benzdeus.
Vulnerability Overview
The ELEX WordPress HelpDesk & Customer Ticketing System plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 3.3.5. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform an unauthorized action.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in ELEX WordPress HelpDesk & Customer Ticketing System <= 3.3.5 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For ELEX WordPress HelpDesk & Customer Ticketing System the fix is 3.3.6: builds <= 3.3.5 are affected, anything from 3.3.6 onward is not.
Remediation
Update to version 3.3.6, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: ELEX WordPress HelpDesk & Customer Ticketing System 3.3.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 8.8CVE-2024-12171: ELEX WordPress HelpDesk… Authenticated (Subscriber+)
CVE-2024-12171 - 5.3CVE-2025-14079: ELEX WordPress HelpDesk… Authenticated (Subscriber+)
CVE-2025-14079 - 4.3CVE-2025-12023: ELEX WordPress HelpDesk… Authenticated (Subscriber+)
CVE-2025-12023 - 4.3CVE-2025-12085: ELEX WordPres… Authenticated (Subscriber+) Trash Empty
CVE-2025-12085
Other vulnerabilities in ELEX WordPress HelpDesk & Customer Ticketing System
- 9.8CVE-2025-11456: ELEX WordPress HelpDesk… Arbitrary File Upload
CVE-2025-11456 - 8.8CVE-2025-47658: ELEX WordPress HelpDesk… Arbitrary File Upload
CVE-2025-47658 - 7.2CVE-2025-9343: ELEX WordPress HelpDesk & Customer… Stored XSS
CVE-2025-9343 - 6.5CVE-2026-48964: ELEX WordPress HelpDesk & Customer… SQL Injection
CVE-2026-48964 - 6.3CVE-2025-13534: ELEX WordPress HelpDesk… Privilege Escalation
CVE-2025-13534 - 4.3CVE-2025-12022: ELEX WordPress HelpDesk… Authenticated (Subscriber+)
CVE-2025-12022 - 4.3CVE-2025-12169: ELEX WordPress HelpDesk… Authenitcated (Subscriber+)
CVE-2025-12169 - 4.3CVE-2025-10054: ELEX WordPress HelpDesk… Authenticated (Subscriber+)
CVE-2025-10054
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C