CVE
ELEX WordPress HelpDesk & Customer Ticketing System PHP object injection in ticketing plugin
Affects the ELEX WordPress HelpDesk & Customer Ticketing System plugin, versions 3.3.9 and earlier. Fixed in 3.4.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Exploited
- Public exploit code, no confirmed attacks
- Fix
- Fixed in 3.4.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.4.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- First public exploit on GitHub Nov 14
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.41% · 35th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 52/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
The ELEX WordPress HelpDesk & Customer Ticketing System plugin for WordPress, published by Elextensions, is affected by a PHP object injection flaw caused by unsafe deserialization of untrusted data. An attacker can exploit it remotely, without logging in, to inject crafted objects into the plugin, which may let them compromise the site.
Original description
Deserialization of Untrusted Data vulnerability in Elextensions ELEX WordPress HelpDesk & Customer Ticketing System elex-helpdesk-customer-support-ticket-system allows Object Injection.This issue affects ELEX WordPress HelpDesk & Customer Ticketing System: from n/a through 3.3.9.
cve.now Index
- Exploitation22/40Public exploit on Exploit-DB or GitHub
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 57 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.4.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-125855 (WordPress ELEX WordPress HelpDesk & Customer Ticketing System plugin <= 3.3.9 - PHP Object Injection vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-125855 (entry last updated 2026-11-13):
Affected:
- Elextensions ELEX WordPress HelpDesk & Customer Ticketing System: through 3.3.9
Fixed versions: 3.4.0.
Conditions (all must be true for the bug to be hit):
- ELEX WordPress HelpDesk & Customer Ticketing System plugin version 3.3.9 or earlier (source: https://patchstack.com/database/wordpress/plugin/elex-helpdesk-customer-support-ticket-system/vulnerability/wordpress-elex-wordpress-helpdesk-customer-ticketing-system-plugin-3-3-9-php-object-injection-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-125855 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125855 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/elex-helpdesk-customer-support-ticket-system/vulnerability/wordpress-elex-wordpress-helpdesk-customer-ticketing-system-plugin-3-3-9-php-object-injection-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-125855
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-125855
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125855"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
- Posted on X by cve.now1 day
- Exploit code on GitHub
im0xfay/CVE-2026-125855
Affected versions
- elex-helpdesk-customer-support-ticket-system
through 3.3.9
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125855
Is CVE-2026-125855 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data
What does this mean?
This is a PHP Object Injection flaw in the plugin. The advisory says attackers can manipulate how the site processes data to run harmful actions on the server.Source: patchstack.com, cve.org
Which versions are affected by CVE-2026-125855?
elex-helpdesk-customer-support-ticket-system: through 3.3.9.Source: cve.now feed data
Am I affected, and how do I check?
The plugin versions 3.3.9 and earlier are listed as vulnerable. To check a site, look at the plugin's version number on the WordPress Plugins screen.Source: patchstack.com, cve.org
How do I fix CVE-2026-125855?
Update the ELEX WordPress HelpDesk & Customer Ticketing System plugin to version 3.4.0 or later, the fixed version the advisory names.Source: patchstack.com, cve.org