On this page (7 sections)
A critical vulnerability, tracked as CVE-2026-119077, affects the ELEX WordPress HelpDesk & Customer Ticketing System plugin in all versions up to and including 3.3.9. According to the GitHub advisory and the NVD record, it is a PHP Object Injection flaw that could let unauthenticated attackers execute code on the server.
If your WordPress site uses this plugin to run a support desk or ticket form, treat it as urgent. The advisory does not list a patched version, so the safest assumption today is that you need to restrict or remove the plugin until the vendor confirms a fix.
What happened
The vulnerability was published on November 13, 2026 by the National Vulnerability Database and the GitHub Advisory Database. The description says the plugin deserializes attacker-controlled data without checking who is sending it and without limiting which classes can be created. The affected input is the ticket_label field inside a url-encoded form string.
The only protection described is a nonce, a short-lived token WordPress uses to confirm a request came from a legitimate page. In this case, the nonce (named wsdesk_nonce) is publicly emitted on any page that carries the [wsdesk_support] shortcode. Anyone can load such a page and read it, so it does not work as real authentication.
Technical details in plain terms
PHP Object Injection happens when an application takes text supplied by a visitor and turns it back into live PHP objects (deserialization). If the code does not restrict which object types are allowed, an attacker can supply data that makes PHP build objects the developer never intended. Whether this leads to code execution depends on which classes exist in the application and its libraries, because their built-in behavior can be chained into harmful actions.
Here the advisory says the combination of missing server-side authentication and no class allowlist makes code execution on the server possible. It describes the attack as needing one anonymous GET request to a public page with the shortcode, to read the nonce, followed by one unauthenticated POST request. The CVSS vector reflects this: network attack, low complexity, no privileges, no user interaction, and high impact on confidentiality, integrity and availability.
The advisory references several files in the 3.3.8 plugin source, including the plugin's AJAX handlers and a bundled Guzzle FileCookieJar class, as well as a trunk changeset touching the public functions file. The research does not say whether that changeset is a complete fix or which release, if any, contains it. We are not publishing any exploit detail beyond what the advisory states. The Wordfence entry is also referenced for further reading.
Who is affected
Any WordPress site with the plugin installed at version 3.3.9 or earlier is in scope. The advisory ties the exposed nonce to pages carrying the [wsdesk_support] shortcode, so sites that publish a public support or ticket page are the clearest candidates. The advisory does not say whether a site with the plugin active but no such page is safe, so do not assume it is.
Support desks tend to hold customer names, emails and message content, and often sit on the same server as the rest of the business site. Code execution on that server could expose far more than the ticket data.
How to check your exposure
First confirm whether the plugin is installed and which version it runs. This WP-CLI command is read-only. Run it from your WordPress root as the site user and look for a plugin named elex-helpdesk-customer-support-ticket-system in the output, with a version of 3.3.9 or lower.
wp plugin list --fields=name,status,version,updateNext, find pages that use the shortcode. This read-only query lists published posts and pages whose content contains it. A result means a public page is likely emitting the nonce the advisory describes.
wp post list --post_type=page,post --post_status=publish --s=wsdesk_support --fields=ID,post_title,post_nameThe search may miss shortcodes inserted by page builders or widgets, so also check the WordPress admin plugin screen if you do not have command line access.
What to do now
- Identify every site you manage that runs the ELEX HelpDesk & Customer Ticketing System plugin and note its version.
- Check the plugin's page in the WordPress plugin directory and the vendor's channels for a release newer than 3.3.9 that names this CVE. None is confirmed in the sources we reviewed.
- If a patched release is confirmed, back up the site, update, then re-run the version check above.
- If no fixed release exists, deactivate and remove the plugin, or at least unpublish pages that use [wsdesk_support], until the vendor ships a fix. Unpublishing alone may not be enough, so removal is the safer choice.
- Review web server logs for unusual POST requests to admin-ajax.php or to your support page, especially from IP addresses that also fetched the support page just before.
- Look for signs of compromise: unknown admin users, recently changed PHP files, unfamiliar files in wp-content/uploads, and unexpected scheduled tasks.
- If you find signs of compromise, rotate WordPress, database and hosting passwords and secret keys, and restore from a clean backup.
- Consider a web application firewall rule set that can virtually patch known plugin flaws while you wait for a vendor fix.
Detection and monitoring
Because the attack is described as one GET followed by one POST, it can look like normal traffic in logs. Rather than hunting for a single signature, watch for patterns: a request to the support page followed closely by a POST from the same address to the AJAX endpoint, and any POST whose form body is unusually large or contains serialized-looking data. This read-only search lists POST requests to the AJAX endpoint in a common Apache or nginx access log. Adjust the path to your server and review the sources and timing of the results.
grep 'POST /wp-admin/admin-ajax.php' /var/log/nginx/access.log | tail -n 200Legitimate visitors also use that endpoint, so many results are expected. Focus on unfamiliar IP addresses and bursts of requests around the time the advisory was published or later. A file integrity review after any suspicious activity helps confirm whether code was changed.
For ongoing coverage, an outside-in security scan can flag outdated or risky components on sites you verify, and monitoring can alert you to unexpected changes. Neither replaces patching or removing the vulnerable plugin. Our guide on checking whether a WordPress plugin is vulnerable explains how to track advisories for the plugins you run.
What we still do not know
- Whether a patched plugin release exists. The GitHub advisory lists patched versions as unknown.
- Whether the trunk changeset referenced in the advisory fully resolves the issue.
- Whether the flaw is being exploited. No source reviewed reports attacks, and the entry is not in CISA's KEV list as far as the research shows.
- The exact chain of classes that leads to code execution. The advisory states the outcome but the sources reviewed do not describe it.
We will treat this as an open situation: until the vendor or a trusted advisory confirms a fixed version, the conservative path is to remove or disable the plugin on any site where a public ticket page exists.
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.
