On this page (7 sections)

A critical vulnerability, tracked as CVE-2026-114630, affects the ELEX WordPress HelpDesk & Customer Ticketing System plugin in all versions up to and including 3.3.8. According to the GitHub Advisory Database entry, an unauthenticated attacker can delete arbitrary files on the server, which the advisory says can easily lead to remote code execution when the right file is deleted, such as wp-config.php.

If your site uses this plugin for a support desk or ticket form, treat it as urgent. At the time of writing the advisory lists no patched version, so the safest immediate step is to deactivate the plugin until a vendor fix is confirmed.

What happened

The flaw was published on November 6, 2026 to the National Vulnerability Database and the GitHub Advisory Database. The advisory describes insufficient file path validation in the plugin's factory_reset function. The GitHub entry is marked unreviewed, and the NVD record repeats the same text, so there is effectively one underlying description so far rather than several independent confirmations.

The advisory also references a Wordfence threat intelligence entry and a change to the plugin's trunk code in class-crm-init-handler.php on the WordPress.org Trac. The research does not say whether that change is the official fix or which release will contain it, so do not assume a patched version exists until the plugin's changelog says so.

How the weakness works

This is a path traversal class problem (CWE-22) combined with a missing permission check. In plain terms, the plugin lets a user-supplied value decide which file gets removed, and the routine that performs the removal does not verify that the visitor is an administrator.

The advisory describes a two-step chain. First, an unauthenticated visitor stores a chosen file path value by submitting a ticket through a public AJAX endpoint (eh_crm_new_ticket_post), whose nonce the advisory says is publicly exposed via the [wsdesk_support] shortcode. Second, the attacker triggers the factory reset routine with a GET request to an admin page. That routine is guarded only by is_admin(), a request-type check rather than a capability check, so unlink() is called on the attacker-supplied path.

General WordPress background, not from the advisory: is_admin() only tells code that a request is for an admin screen. It does not prove the user is logged in or authorized. Capability checks such as current_user_can() are what should protect destructive actions.

The advisory gives wp-config.php as its example of a file whose deletion can easily lead to remote code execution. As general background (not the advisory's own explanation), a WordPress site missing its configuration file usually stops working normally and may show the installation screen. Deleting other files could also break the site; the advisory does not list which files are reachable beyond saying arbitrary files can be deleted.

Who is realistically exposed

  • Sites with the ELEX HelpDesk plugin (slug elex-helpdesk-customer-support-ticket-system) installed at version 3.3.8 or earlier.
  • Sites that use the [wsdesk_support] shortcode. The advisory says the nonce needed for the first step is exposed through it. It does not say whether the attack is limited to such sites, so do not treat the absence of the shortcode as proof of safety.
  • Agencies and hosts managing many WordPress sites, where a support plugin may have been installed long ago and forgotten.
  • The research does not say whether a deactivated but still installed copy can be attacked. As general good practice, remove plugins you no longer use.

The CVSS vector rates attack complexity as low, with no privileges and no user interaction required, and the impact is rated high for integrity and availability, with no confidentiality impact. The score does not tell you whether anyone is exploiting the flaw. No source in the research confirms that.

How to check if you are affected

Start by listing the plugin and its version. This read-only WP-CLI command, run from your WordPress root, shows whether the plugin is installed, its status and its version. Look for a version of 3.3.8 or lower.

List the ELEX HelpDesk plugin and its version (run in the WordPress root)WP-CLI
wp plugin list --name=elex-helpdesk-customer-support-ticket-system --fields=name,status,version

Next, see where the public ticket form lives. This read-only query lists posts and pages whose content matches the shortcode name, which helps you understand how the plugin is used on your site.

Find content that uses the [wsdesk_support] shortcode (run in the WordPress root)WP-CLI
wp post list --post_type=any --s='wsdesk_support' --fields=ID,post_title,post_status

Then review your web server logs for requests to the factory reset admin page. The command below searches nginx access logs, including rotated ones, for that page name and prints any matching lines. For Apache on Debian or Ubuntu, logs are commonly under /var/log/apache2/ instead; adjust the path to your setup. Any hit from an unfamiliar address deserves investigation. No hits does not prove safety, since logs may be rotated away or disabled.

Search nginx access logs for requests to the factory reset page (adjust the log path)Shell
grep -i 'wsdesk_factory_reset' /var/log/nginx/access.log*

What to do now

Because no fixed version is listed, either update to a release that the vendor's changelog confirms fixes this issue, or deactivate the plugin until one exists. Check the plugin's page and changelog on WordPress.org before deciding.

Caution. Deactivating or deleting a plugin removes your support form and may affect ticket handling. Export any ticket data you need and take a full backup of files and database first.
  1. Confirm whether the plugin is installed and which version runs, using the WP-CLI command above.
  2. Check the plugin's changelog on WordPress.org for a release newer than 3.3.8 that explicitly mentions this issue, and update if one exists.
  3. If no confirmed fix is available, deactivate the plugin. Removing the shortcode page alone is unverified as a mitigation, because the advisory does not say it prevents exploitation.
  4. Take a full backup (files and database) and store a copy off the server.
  5. Verify wp-config.php and other core files are present and unmodified compared with a known-good copy.
  6. Review access logs for requests to the wsdesk_factory_reset page and for unusual ticket submissions.
  7. Restrict file permissions so the web server user cannot modify files it does not need to write.
  8. Rotate database credentials and WordPress salts if you find signs of tampering or file loss.
  9. Remove plugins you no longer use as general hygiene.
Tip. A web application firewall can add a layer of protection by filtering suspicious requests to admin pages from unauthenticated visitors, but it is not a substitute for deactivating or patching a vulnerable plugin. See what a WAF is for what it can and cannot do.

Detection and monitoring afterwards

Watch for sudden site errors, an installation screen appearing on a live site, or missing core files, which would be consistent with file deletion. Keep file integrity checks and regular backups so you can restore quickly. You can also track plugin issues on the known WordPress plugin vulnerabilities page and review the WordPress security checklist for broader hardening.

For ongoing visibility, Webforta Monitor can alert you to uptime problems, which is often the first visible sign when a site loses critical files. It does not detect or block this specific flaw, so pair it with deactivation or patching and log review.

What we do not know yet

  • No patched version is named in the advisory.
  • No source in the research confirms active exploitation.
  • It is unconfirmed whether removing the shortcode page prevents exploitation, and whether a deactivated plugin can be attacked.
  • Only the advisory text and its NVD copy are available; there is no independent technical write-up in the research.
  • The vendor's own statement is not included in the research.

Treat any fixed version as unconfirmed until the plugin's official changelog or a vendor advisory says so, and re-check the plugin page regularly for updates.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-114630 - GitHub Advisory Databasegithub.com
  2. CVE-2026-114630: The ELEX WordPress HelpDesk & Customer Ticketing System plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation…nvd.nist.gov ·
  • WordPress
  • CVE-2026-114630
  • ELEX HelpDesk
  • file deletion
  • plugin vulnerability