Skip to content
ELEX HelpDesk CVE-2026-119077: Update public support forms

ELEX HelpDesk CVE-2026-119077: Update public support forms

November 13, 2026

Update ELEX WordPress HelpDesk & Customer Ticketing System installations running version 3.3.9 or earlier. Wordfence rates CVE-2026-119077 at CVSS 3.1 9.8 (Critical) and reports possible unauthenticated server-side code execution. Its CNA record dates disclosure to November 12, 2026 at 21:10:29 UTC. The CVE record followed on November 13 at 09:35:17 UTC.

Check version and public exposure

In WordPress, open Plugins > Installed Plugins and record the ELEX version and activation status. For multisite, check network activation and each site’s support pages. The plugin directory name is elex-helpdesk-customer-support-ticket-system.

The CNA describes missing server-side authentication and PHP object deserialization without a class allowlist. The reported attack requires anonymous access to a page exposing the [wsdesk_support] support form. Find those pages in your site’s content and configuration, including translated copies. Do not submit exploit payloads to test exposure.

The vendor plugin page lists 3.4.0 and a security fix. Its changelog does not name this CVE. Wordfence marks versions through 3.3.9 as affected, so use 3.4.0 or a later compatible, supported release.

Check release metadata on Linux

This example downloads the vendor’s public readme and prints its release fields. It does not inspect or change a WordPress installation. You need Python 3 and curl.

Create a temporary working directory, then download the vendor readme:

workdir=$(mktemp -d) && cd "$workdir" && \
curl -fSs --connect-timeout 10 --max-time 30 \
  -o elex-release-readme.txt \
  https://plugins.svn.wordpress.org/elex-helpdesk-customer-support-ticket-system/trunk/readme.txt

Stop if setup or download fails. Keep the same shell for the remaining steps. Save this as elex_release_note.py:

from pathlib import Path
import re

try:
    readme = Path("elex-release-readme.txt").read_text(encoding="utf-8")
except (OSError, UnicodeError) as error:
    raise SystemExit(f"Cannot read release metadata: {error}")

stable = re.search(r"^Stable tag: ([0-9]+\.[0-9]+\.[0-9]+)$", readme, re.M)
note = re.search(r"^= 3\.4\.0 =\n\* ([^\n]+)", readme, re.M)
if not stable or not note:
    raise SystemExit("Expected release fields missing; check the vendor page manually.")
print(f"Stable tag: {stable[1]}")
print(f"3.4.0: {note[1]}")
print("Release metadata only; the installed plugin was not inspected.")

Run:

python3 elex_release_note.py

Observed on Debian 13 with Python 3.12.14, November 13, 2026, exit status 0:

Stable tag: 3.4.0
3.4.0: Security fix: Resolved a vulnerability issue.
Release metadata only; the installed plugin was not inspected.

An unreadable file or missing expected fields produces an error and exit status 1. Future releases may change this output. Remove only the scratch files and empty directory when finished:

rm -- elex_release_note.py elex-release-readme.txt
cd /
rmdir -- "$workdir"
unset workdir

Update and verify ticket handling

Before updating, create a restorable backup of the database and site files, including configuration and ticket attachments. Store it outside the public web root. WordPress’s backup guidance explains why both database and files are needed.

Check compatibility with your WordPress and PHP versions. Test the update on staging if available, with outbound mail routed to a test mailbox. Then use Plugins > Installed Plugins > Update now for ELEX, following the WordPress update procedure. Confirm the installed version after completion.

Submit an ordinary test ticket with non-sensitive data. Verify that the agent can read and reply to it, and that expected notifications arrive. Check PHP logs for new errors. If you cannot update promptly, deactivate the plugin and provide another support channel; deactivation interrupts ticket intake. Avoid uninstalling it as a temporary measure because removal can affect stored data.

Only the metadata helper was executed here. No WordPress update or exploit was tested, and the cited records do not establish active exploitation. A successful update does not rule out earlier compromise; investigate unexpected administrator accounts or file changes separately.

Acknowledgements

This post was created with assistance from AI.

Last updated on