CVE-2025-10039

ELEX WordPress HelpDesk & Customer Ticketing System <= 3.2.9 - Authenticated (Subscriber+) Insecure Direct Object Reference via 'eh_crm_ticket_single_view_client'

2025-11-20 00:00
Athiwat Tiprasaharn (Jitlada)

Strategic Overview

Status
Patched in 3.3.0
Affected Plugin
ELEX WordPress HelpDesk & Customer Ticketing System
Affected Version
<= 3.2.9
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2025-10039
View all ELEX WordPress HelpDesk & Customer Ticketing System vulnerabilities

At a glance

CVE-2025-10039 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the ELEX WordPress HelpDesk & Customer Ticketing System WordPress plugin, affecting versions <= 3.2.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.3.0; sites on affected versions should update now. Disclosed November 2025, reported by Athiwat Tiprasaharn (Jitlada).

Vulnerability Overview

The ELEX WordPress HelpDesk & Customer Ticketing System plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.2.9 via the 'eh_crm_ticket_single_view_client' due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the contents of all support tickets.

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-639: Authorization Bypass Through User-Controlled Key

ELEX WordPress HelpDesk & Customer Ticketing System <= 3.2.9 carries this weakness at eh_crm_ticket_single_view_client, and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For ELEX WordPress HelpDesk & Customer Ticketing System the fix is 3.3.0: builds <= 3.2.9 are affected, anything from 3.3.0 onward is not.

Remediation

Update to version 3.3.0, 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.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-10039https://www.wordfence.com/threat-intel/vulnerabilities/id/d9ffc0af-9c3d-4f8e-ae0b-e51c0c67dfe1https://nvd.nist.gov/vuln/detail/CVE-2025-10039

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C