The Coe Lab
← Back to Security

CVE-2026-114630: ELEX WordPress HelpDesk plugin lets unauthenticated visitors delete arbitrary files — update to 3.3.9

By November 9, 20269 min read
CVE AnalysisCVE-2026-114630Cybersecurity
A technology notebook with visual symbols for AI, cybersecurity, infrastructure, and automation

Anyone can chain two unauthenticated requests to delete files on servers running ELEX WordPress HelpDesk & Customer Ticketing System 3.3.8 and earlier. Version 3.3.9 fixes it; update now.

CoeLab Real-World Impact: 81/100 — High. Editorial score v1.0. Evidence checked 2026-11-09T16:10:31.163505+00:00. CVSS and EPSS are separate measures, not this editorial score.

Rating breakdown: exploitation: 18, reachability: 25, consequences: 23, operational relevance: 15.

Who is affected

The flaw lives in the ELEX WordPress HelpDesk & Customer Ticketing System plugin (internally branded WSDesk), sold by ELEXtensions. According to the CVE record maintained with Wordfence as the numbering authority, every released version up to and including 3.3.8 is affected; version 3.3.9 is explicitly outside the affected range, and it is the version currently published on WordPress.org. The plugin's release history confirms 3.3.8 and 3.3.9 as consecutive tags, so 3.3.9 is the first available fixed release.

Any WordPress site where the plugin is active in an affected version is exposed to the unauthenticated attack path described below, regardless of whether the site's administrators are careful — the vulnerable code path requires no credentials and no user interaction. WordPress.org currently lists roughly 200 active installations for this plugin, so the raw population of directly exposed sites is small. That context matters for proportion: this is a serious flaw for each affected site, not a mass event like a flaw in a plugin with tens of millions of installs.

Real-world impact and exploitation evidence

The bug is an arbitrary file deletion: an attacker chooses a filesystem path, and the running PHP process deletes whatever file sits at that path. On shared-hosting and typical single-site WordPress servers, the webserver user can write to wp-config.php and other WordPress core files, so deleting the right file turns a cleanup bug into a real route to code execution — remove wp-config.php and many setups will then walk an attacker through a setup screen that accepts a new database and, on misconfigured stacks, writes back to the same server. That framing comes from the CVE description itself; no exploit code, testing, or weaponization is involved in this analysis.

On exploitation evidence: as of November 9, 2026 there is no entry in CISA's Known Exploited Vulnerabilities catalog, the CISA coordination record marks exploitation as 'none', and FIRST's Exploit Prediction Scoring System estimates about a 1.3 percent probability of exploitation within 30 days (71st percentile). That is elevated above typical but far from a signal that attacks are underway. Practical impact right now is best stated as severe-if-exploited with no confirmed in-the-wild exploitation at time of writing.

Attack prerequisites

The chain is notable for what it does not require: no account, no privilege, no user interaction. The CVE record describes a two-step sequence. First, an unauthenticated visitor stores an arbitrary attachment path by submitting a ticket through the plugin's public AJAX ticket-creation endpoint, whose nonce is handed out by the ticket form shortcode the plugin normally renders on the site. Second, the attacker triggers the plugin's factory-reset routine, which calls unlink() on the stored path. The reset routine checks only that the request came through the admin URL structure — a request-type check — rather than verifying that the caller holds an administrative capability.

In CVSS terms the record carries CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N with an integrity and availability focus (C:N/I:H/A:H), scoring 9.1 CRITICAL. The CoeLab Real-World Impact score for this candidate is 81 (High): 18 for exploitation (EPSS ≈1.3 percent, an intermediate signal, not proof of active attacks), 25 for reachability (network vector, low complexity, no privileges or interaction), 23 for consequences (driven by the 9.1 base score), and 15 for operational relevance (plugin category match). Two limitations are worth carrying forward. The score inherits EPSS's statistical nature — it predicts likelihood, not observed exploitation — and the operational-relevance component is a category heuristic, not a measurement of how many sites actually run this plugin; the WordPress.org install count (~200) is much smaller than the category weight alone would suggest. The score is neither CVSS nor EPSS and does not describe anyone's actual environment.

Actions and fixes

Update ELEX WordPress HelpDesk & Customer Ticketing System to 3.3.9 or later; 3.3.8 and every earlier release is affected, and 3.3.9 is the confirmed fixed version. That is the complete remediation for most operators, and because the attack path is unauthenticated and the affected code path does not depend on configuration, there is no documented partial mitigation in the primary sources — removing the plugin entirely, if it is unused, is the alternative that actually removes the vulnerable code rather than narrowing the window.

Two housekeeping steps are worth pairing with the update. First, the factory-reset routine deletes files as a designed behavior, so after updating, verify that the reset page is not reachable from public traffic in your configuration. Second, if a site ran an affected version for any length of time, check for signs of abuse: missing or modified core files such as wp-config.php, unexpected 500 errors, or tickets whose attachment fields contain odd paths. Log review here is defensive housekeeping, not a claim that any particular site was targeted.

Uncertainty and what could change

The main open question is the install base. WordPress.org's active-install counter (~200) reflects tracked public-repository installations and may not capture premium deployments of the vendor's separately sold products; the CVE record itself does not publish install figures. Similarly, the absence of KEV listing and an 'exploitation: none' coordination tag describe the situation as of November 6–9, 2026; either can change. If exploitation evidence, a KEV addition, or a wider affected range appears, that justifies an updated analysis — but none of that is asserted today.

Another wrinkle worth naming for editors and operators alike: the numbering-authority record was updated on November 6, 2026, the day after public disclosure, so later record revisions are plausible. Details specific to how fixed versions validate attachment paths are drawn from the cited record and public plugin repository states; we did not independently test any version, and our statements about 3.3.9 being fixed rest on the record's version range plus the public release history, not on our own differential analysis.

Sources and evidence date

Primary evidence used for this analysis, all accessed November 9, 2026: the CVE record for CVE-2026-114630 including the Wordfence numbering-authority container (reserved October 21, 2026; published November 6, 2026; updated November 6, 2026), which supplies the affected-version range, the two-step unauthenticated chain, the CVSS 3.1 vector and score, and the disclosure timeline: vendor notified October 21, 2026, public disclosure November 5, 2026. CISA's ADP annotation in the same record provides the SSVC coordination decision (exploitation: none; automatable: yes).

Version and release-state evidence comes from the official WordPress.org plugin information API, which lists 3.3.9 as the current release, and the official plugin SVN tag listing, which confirms 3.3.8 and 3.3.9 are consecutive tags with no other release between them. EPSS values (≈1.3 percent, 71st percentile, dated November 9, 2026) come from FIRST's public data as processed by the CoeLab intake pipeline; the CoeLab Real-World Impact score of 81 and its component breakdown are The Coe Lab's own scoring framework and are not vendor or FIRST output. The KEV status (absent) reflects CISA's catalog as of November 9, 2026.

Primary-source links

https://www.cve.org/CVERecord?id=CVE-2026-114630

https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/114xxx/CVE-2026-114630.json

https://api.wordpress.org/plugins/info/1.2/?action=plugin_information&request%5Bslug%5D=elex-helpdesk-customer-support-ticket-system

https://plugins.svn.wordpress.org/elex-helpdesk-customer-support-ticket-system/tags/

AI-assisted research and drafting, with a separate model editorial review. CoeLab ratings are editorial judgments, not a substitute for checking your own versions and vendor advisories. Methodology: https://thecoelab.com/blog/security/methodology

Related Posts

CVE-2026-123890: VMware vCenter authentication bypass exploited since September — CISA patch deadline is November 23

A critical unauthenticated vCenter Directory Service flaw was used in real intrusions weeks before disclosure. CISA gives federal agencies until November 23 — everyone else should not wait longer.

Nov 22, 2026• 12 min

Your USB-C Dock Is Part of Your Network. Test It That Way.

A trending Ethernet investigation shows why docks belong in your network diagram. Here is how to isolate bottlenecks before replacing routers or adapters.

Nov 22, 2026• 9 min

CVE-2026-129448: Apache Roller XML-RPC deserialization gets CISA KEV deadline — unauthenticated remote code execution in versions before 6.1.5

Apache Roller before 6.1.5 runs unauthenticated XML-RPC deserialization before authentication; it is now on CISA's exploited list with a patch deadline of November 23, 2026.

Nov 21, 2026• 11 min