# CVE-2024-7728: CAYIN Technology CMS - OS Command Injection

> Remote attackers with admin privileges can inject OS commands into CAYIN Technology CMS via improper input validation in a CGI script.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2024
- **Updated:** 14 Aug 2024
- **Also known as:** GHSA-5prx-vp4c-c7vg

## What is CVE-2024-7728?

CVE-2024-7728 is a high-severity command injection vulnerability in CAYIN Technology CMS-SE, published on 14 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The specific CGI of the CAYIN Technology CMS does not properly validate user input, allowing a remote attacker with administrator privileges to inject OS commands into the specific parameter and execute them on the remote server.

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

## Which versions are affected by CVE-2024-7728?


## How do I fix CVE-2024-7728?

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

## Is CVE-2024-7728 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7728 and fix it if it is affected.

What it is: CVE-2024-7728 is a high-severity command injection vulnerability in CAYIN Technology CMS-SE, published on 14 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7728 in the wild and no public exploit code.

Affected product: CAYIN Technology CMS-SE. 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-2024-7728/ (Markdown: https://insights.sbomify.com/CVE-2024-7728/index.md)
```

## Sources

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

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