# CVE-2023-53935: WBiz Desk 1.2 SQL Injection Vulnerability via ticket.php Parameter

> Non-admin users can exploit SQL injection in WBiz Desk to extract sensitive database information via the ticket.php endpoint.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA: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:** 18 Dec 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-97c9-gh8x-2vv2

## What is CVE-2023-53935?

CVE-2023-53935 is a medium-severity SQL injection vulnerability in Codester WBiz Desk, published on 18 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WBiz Desk 1.2 contains a SQL injection vulnerability that allows non-admin users to manipulate database queries through the 'tk' parameter in ticket.php. Attackers can inject crafted SQL statements using UNION-based techniques to extract sensitive database information by sending malformed requests to the ticket endpoint.

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

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


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

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

## Is CVE-2023-53935 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-53935 is a medium-severity SQL injection vulnerability in Codester WBiz Desk, published on 18 Dec 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-2023-53935 in the wild and no public exploit code.

Affected product: Codester WBiz 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-53935/ (Markdown: https://insights.sbomify.com/CVE-2023-53935/index.md)
```

## Sources

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

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