# CVE-2023-7116: WeiYe-Jing datax-web HTTP POST Request killJob os command injection

> Remote attackers can execute arbitrary OS commands via the processId parameter in the killJob endpoint of datax-web.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 27 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-phr5-43p5-mfwq

## What is CVE-2023-7116?

CVE-2023-7116 is a medium-severity command injection vulnerability in WeiYe-Jing datax-web, published on 27 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in WeiYe-Jing datax-web 2.1.2. Affected by this issue is some unknown functionality of the file /api/log/killJob of the component HTTP POST Request Handler. The manipulation of the argument processId leads to os command injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-249086 is the identifier assigned to this vulnerability.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Datax-Web Project Datax-Web.

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

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

## Is CVE-2023-7116 being exploited?

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

Public exploit code:

- WeiYe-Jing datax-web <= 2.1.2 - OS Command Injection (nuclei): http/cves/2023/CVE-2023-7116.yaml

## Other vulnerabilities in WeiYe-Jing datax-web

- [CVE-2022-46478](https://insights.sbomify.com/CVE-2022-46478/): Deserialization in n/a (critical 9.8)
- [CVE-2025-13250](https://insights.sbomify.com/CVE-2025-13250/): WeiYe-Jing datax-web Job triggerJob access control (medium 5.3)
- [CVE-2025-13251](https://insights.sbomify.com/CVE-2025-13251/): WeiYe-Jing datax-web sql injection (medium 5.3)
- [CVE-2024-12358](https://insights.sbomify.com/CVE-2024-12358/): WeiYe-Jing datax-web add os command injection (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-7116 is a medium-severity command injection vulnerability in WeiYe-Jing datax-web, published on 27 Dec 2023. 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-7116 exists.

Affected product: WeiYe-Jing datax-web. 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-7116/ (Markdown: https://insights.sbomify.com/CVE-2023-7116/index.md)
```

## Sources

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

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