# CVE-2023-52163: Digiever DS-2105 Pro Missing Authorization

> Attackers can execute arbitrary commands on unsupported Digiever DS-2105 Pro devices via the time_tzsetup.cgi script.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 22 Dec 2025 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-mrvx-3qrr-qqxw

## What is CVE-2023-52163?

CVE-2023-52163 is a high-severity command injection vulnerability in n/a, published on 3 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Digiever DS-2105 Pro 3.1.0.71-11 devices allow time_tzsetup.cgi Command Injection. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-862 (Missing Authorization)

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

It affects 2 products.


Products: Digiever Ds-2105 Pro\+ Firmware, Digiever Ds-2105 Pro Firmware.

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

No fix has been published for CVE-2023-52163 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 12 Jan 2026.

## Is CVE-2023-52163 being exploited?

Yes. Attackers have exploited CVE-2023-52163 in the wild since at least 22 Dec 2025.

Public exploit code:

- Digiever DS-2105 Pro - Command Injection (nuclei): http/cves/2023/CVE-2023-52163.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2023-52163 is a high-severity command injection vulnerability in n/a, published on 3 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-52163 in the wild since at least 22 Dec 2025.

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-52163/ (Markdown: https://insights.sbomify.com/CVE-2023-52163/index.md)
```

## Sources

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

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