Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14079: CWE-862 Missing Authorization in elextensions ELEX WordPress HelpDesk & Customer Ticketing System

0
Medium
VulnerabilityCVE-2025-14079cvecve-2025-14079cwe-862
Published: Thu Feb 05 2026 (02/05/2026, 09:13:44 UTC)
Source: CVE Database V5
Vendor/Project: elextensions
Product: ELEX WordPress HelpDesk & Customer Ticketing System

Description

The ELEX WordPress HelpDesk & Customer Ticketing System plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.3.5. This is due to missing capability checks on the eh_crm_ticket_general function combined with a shared nonce that is exposed to low-privileged users. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify global WSDesk settings via the `eh_crm_ticket_general` AJAX action.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 10:49:30 UTC

Technical Analysis

CVE-2025-14079 is a vulnerability classified under CWE-862 (Missing Authorization) found in the ELEX WordPress HelpDesk & Customer Ticketing System plugin, affecting all versions up to and including 3.3.5. The root cause is the absence of proper capability checks in the eh_crm_ticket_general AJAX action handler, which is responsible for managing global WSDesk settings. Additionally, the plugin uses a shared nonce that is exposed to users with low privileges, such as Subscribers. This combination allows authenticated users with minimal privileges to bypass authorization controls and modify critical plugin settings. The vulnerability is exploitable remotely via network requests without requiring user interaction or elevated privileges beyond Subscriber level. The CVSS 3.1 base score is 5.3 (medium), reflecting the limited scope of impact—specifically, integrity is affected as attackers can alter settings, but confidentiality and availability remain intact. No patches or fixes are currently linked, and no known exploits have been reported in the wild. The vulnerability underscores a common security oversight in WordPress plugins where capability checks are either missing or improperly implemented, and nonce usage is insecure, leading to privilege escalation risks within authenticated sessions.

Potential Impact

The primary impact of CVE-2025-14079 is the unauthorized modification of global WSDesk plugin settings by low-privileged authenticated users. This can lead to misconfiguration of helpdesk and ticketing workflows, potentially disrupting customer support operations or enabling further attacks through manipulated plugin behavior. While the vulnerability does not directly expose sensitive data or cause denial of service, the integrity compromise can undermine trust in the support system and create operational inefficiencies. Organizations relying on this plugin for customer support risk unauthorized changes that could degrade service quality or facilitate additional exploitation vectors if attackers leverage altered configurations. The medium severity rating reflects the moderate risk, but the ease of exploitation by any authenticated user increases the threat level in environments with many low-privileged users. The lack of known exploits suggests limited active targeting so far, but the vulnerability remains a significant risk until patched.

Mitigation Recommendations

To mitigate CVE-2025-14079, organizations should immediately restrict Subscriber-level users from accessing the affected AJAX action by implementing custom capability checks or disabling the eh_crm_ticket_general action for low-privilege roles via WordPress hooks or filters. Monitoring and logging AJAX requests related to WSDesk settings can help detect unauthorized attempts. Until an official patch is released, consider temporarily removing or disabling the ELEX WordPress HelpDesk & Customer Ticketing System plugin if feasible. Administrators should also audit user roles and permissions to minimize the number of users with authenticated access at Subscriber level or higher. Employing a Web Application Firewall (WAF) with custom rules to block suspicious AJAX requests targeting the vulnerable function can provide additional protection. Finally, maintain vigilance for updates from the vendor and apply patches promptly once available to ensure the vulnerability is fully remediated.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-04T22:50:16.724Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69846323f9fa50a62f145d2b

Added to database: 2/5/2026, 9:30:11 AM

Last enriched: 2/27/2026, 10:49:30 AM

Last updated: 3/22/2026, 3:13:06 PM

Views: 69

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses