# CVE-2025-10039: Information disclosure in ELEX WordPress HelpDesk & Customer Ticketing System

> Authenticated subscribers can read all support tickets due to missing validation in the ELEX WordPress HelpDesk plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Nov 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-68qq-4wv4-qx36

## What is CVE-2025-10039?

CVE-2025-10039 is a medium-severity vulnerability in elextensions ELEX WordPress HelpDesk & Customer Ticketing System, published on 21 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The ELEX WordPress HelpDesk & Customer Ticketing System plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.2.9 via the 'eh_crm_ticket_single_view_client' due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the contents of all support tickets.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2025-10039?

It affects 1 product.


Products: Elula Wsdesk.

## How do I fix CVE-2025-10039?

No fix has been published for CVE-2025-10039 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-10039 being exploited?

There is no known exploitation of CVE-2025-10039 in the wild and no public exploit code.

## Other vulnerabilities in elextensions ELEX WordPress HelpDesk & Customer Ticketing System

- [CVE-2025-47658](https://insights.sbomify.com/CVE-2025-47658/): WordPress ELEX HelpDesk & Customer Ticketing System plugin <= 3.2.9 - Arbitrary File Upload vulnerability (critical 9.9)
- [CVE-2025-11456](https://insights.sbomify.com/CVE-2025-11456/): ELEX WordPress HelpDesk & Customer Ticketing System <= 3.3.1 - Unauthenticated Arbitrary File Upload (critical 9.8)
- [CVE-2024-12171](https://insights.sbomify.com/CVE-2024-12171/): Missing authorization in ELEX WordPress HelpDesk & Customer Ticketing System (high 8.8)
- [CVE-2025-13534](https://insights.sbomify.com/CVE-2025-13534/): Privilege escalation in ELEX WordPress HelpDesk & Customer Ticketing System (medium 6.3)
- [CVE-2025-10054](https://insights.sbomify.com/CVE-2025-10054/): Missing authorization in ELEX WordPress HelpDesk & Customer Ticketing System (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10039 and fix it if it is affected.

What it is: CVE-2025-10039 is a medium-severity vulnerability in elextensions ELEX WordPress HelpDesk & Customer Ticketing System, published on 21 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10039 in the wild and no public exploit code.

Affected product: elextensions ELEX WordPress HelpDesk & Customer Ticketing System. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10039/ (Markdown: https://insights.sbomify.com/CVE-2025-10039/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10039
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10039
- OSV: https://osv.dev/vulnerability/CVE-2025-10039

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10039/
Summaries are generated and may contain mistakes; the official description above is the record.