# CVE-2023-23679: Missing authorization in JS Help Desk

> Attackers can bypass authorization checks to access or modify other users' support tickets in the JS Help Desk WordPress plugin.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Jun 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-f6vx-5rmg-69j9

## What is CVE-2023-23679?

CVE-2023-23679 is a medium-severity missing authorization vulnerability in JS Help Desk, published on 23 Jun 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Authorization Bypass Through User-Controlled Key vulnerability in JS Help Desk js-support-ticket allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects JS Help Desk: from n/a through 2.7.7.

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

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

It affects 1 product.


Products: Jshelpdesk Jshelpdesk.

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

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

## Is CVE-2023-23679 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-23679 is a medium-severity missing authorization vulnerability in JS Help Desk, published on 23 Jun 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-23679 in the wild and no public exploit code.

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

## Sources

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

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