# CVE-2023-39853: SQL injection in n/a

> Remote attackers can exploit SQL injection in Dzzoffice to obtain sensitive information via specific parameters in the Network Disk module.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 6 Jan 2024
- **Updated:** 16 Jun 2025
- **Also known as:** GHSA-5x7g-8gcq-4xxf

## What is CVE-2023-39853?

CVE-2023-39853 is a medium-severity SQL injection vulnerability in n/a, published on 6 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL Injection vulnerability in Dzzoffice version 2.01, allows remote attackers to obtain sensitive information via the doobj and doevent parameters in the Network Disk backend module.

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

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

It affects 1 product.


Products: Dzzoffice Dzzoffice.

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

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

## Is CVE-2023-39853 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-63694](https://insights.sbomify.com/CVE-2025-63694/): SQL injection in n/a (critical 9.8)
- [CVE-2025-63695](https://insights.sbomify.com/CVE-2025-63695/): File upload in n/a (critical 9.8)
- [CVE-2024-41376](https://insights.sbomify.com/CVE-2024-41376/): Path traversal in n/a (high 8.8)
- [CVE-2022-43340](https://insights.sbomify.com/CVE-2022-43340/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2024-29273](https://insights.sbomify.com/CVE-2024-29273/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-39853 is a medium-severity SQL injection vulnerability in n/a, published on 6 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-39853 exists.

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

## Sources

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

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