# CVE-2023-7227: Command Injection vulnerability in SystemK NVR 504/508/516

> Attackers can execute arbitrary commands with root privileges via the DDNS settings in SystemK NVR devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jan 2024
- **Updated:** 29 May 2025
- **Also known as:** GHSA-6485-hpmh-6q3r

## What is CVE-2023-7227?

CVE-2023-7227 is a critical command injection vulnerability in SystemK  NVR 504, published on 25 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SystemK NVR 504/508/516 versions 2.3.5SK.30084998 and prior are vulnerable to a command injection vulnerability in the dynamic domain name system (DDNS) settings that could allow an attacker to execute arbitrary commands with root privileges.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 3 products.


Products: Systemk-Corp Nvr 504 Firmware, Systemk-Corp Nvr 508 Firmware, Systemk-Corp Nvr 516 Firmware.

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

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

## Is CVE-2023-7227 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-7227 is a critical command injection vulnerability in SystemK  NVR 504, published on 25 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-7227 in the wild and no public exploit code.

Affected product: SystemK  NVR 504. 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-7227/ (Markdown: https://insights.sbomify.com/CVE-2023-7227/index.md)
```

## Sources

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

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