# CVE-2023-50839: WordPress JS Help Desk – Best Help Desk & Support Plugin <= 2.8.1 is vulnerable to SQL Injection

> Attackers can execute arbitrary SQL commands via the JS Help Desk plugin, potentially reading or modifying database contents.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Dec 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-3f5j-mfg2-hxvj

## What is CVE-2023-50839?

CVE-2023-50839 is a critical SQL injection vulnerability in JS Help Desk – Best Help Desk & Support Plugin, published on 28 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in JS Help Desk JS Help Desk – Best Help Desk & Support Plugin.This issue affects JS Help Desk – Best Help Desk & Support Plugin: from n/a through 2.8.1.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2023-50839?

It affects 1 product.


Products: Wiselyhub Js Help Desk.

## How do I fix CVE-2023-50839?

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

## Is CVE-2023-50839 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50839 exists.

Public exploit code:

- Bug Bounty: CVE-2023-50839 IDOR identified in a third-party support component via 'gau' and 'Nuclei'. Despite perimeter redirects, the outdated software remained exposed. Confirmed through manual header analysis. Severity: 5.3 (Medium). Focused on Defense in Depth failures and PII protection. Status: Reported on Intigriti. (github_poc): https://github.com/Francesco-CyberIntelligence/bug-bounty-findings-o-research-disclosures.
- JS Help Desk <= 2.8.1 - SQL Injection (nuclei): http/cves/2023/CVE-2023-50839.yaml

## Other vulnerabilities in JS Help Desk – Best Help Desk & Support Plugin

- [CVE-2022-46839](https://insights.sbomify.com/CVE-2022-46839/): WordPress JS Help Desk – Best Help Desk & Support Plugin Plugin <= 2.7.1 is vulnerable to Arbitrary File Upload (critical 10.0)
- [CVE-2024-13606](https://insights.sbomify.com/CVE-2024-13606/): Information disclosure in JS Help Desk – AI-Powered Support & Ticketing System (high 7.5)
- [CVE-2022-46842](https://insights.sbomify.com/CVE-2022-46842/): WordPress JS Help Desk plugin <= 2.7.1 is vulnerable to Cross Site Request Forgery (CSRF) (medium 5.4)
- [CVE-2024-31273](https://insights.sbomify.com/CVE-2024-31273/): WordPress JS Help Desk plugin <= 2.8.3 - Broken Access Control vulnerability (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-50839 and fix it if it is affected.

What it is: CVE-2023-50839 is a critical SQL injection vulnerability in JS Help Desk – Best Help Desk & Support Plugin, published on 28 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50839 exists.

Affected product: JS Help Desk – Best Help Desk & Support Plugin. 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-2023-50839/ (Markdown: https://insights.sbomify.com/CVE-2023-50839/index.md)
```

## Sources

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

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