CVE-2025-10054 MEDIUM

CVE-2025-10054: ELEX WordPress HelpDesk & Customer Ticketing System <= 3.3.1 - Missing Authorization to Authenticated (Subscriber+) Role Removal

Vendor Elextensions
Product ELEX WordPress HelpDesk & Customer Ticketing System
Weakness CWE-862 · Missing authorization
Published November 21, 2025
Last update April 8, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

The ELEX WordPress HelpDesk & Customer Ticketing System plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'eh_crm_remove_agent' function in all versions up to, and including, 3.3.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to remove the role and capabilities of any user with an Administrator, WSDesk Supervisor, or WSDesk Agents role.

Explanation of Vulnerability in Simple Terms

02Summary

The ELEX WordPress HelpDesk & Customer Ticketing System plugin through version 3.3.1 lacks proper authorization checks on certain functions. A logged-in user with low privileges can modify data they should not have access to, such as ticket information or system settings. The vulnerability requires an active WordPress account but no special permissions. Site administrators should update the plugin immediately.

What an attacker can do

03Attacker Capabilities

A logged-in user can modify ticket data or other protected information they should not have access to.

Potential impact on your site

04Site Impact

Ticket data and helpdesk settings can be altered by any logged-in user, compromising ticket integrity and system configuration.

Conditions required to exploit

05Prerequisites

Attacker must have a valid WordPress user account with low privileges (e.g., subscriber or contributor role).

Key dates

06Disclosure timeline

November 21, 2025 CVE published
April 8, 2026 Record updated