CVE
nginxWebUI remote code execution via login filter bypass in runCmd
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 3.5.8
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.5.8.
Summary
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.
Who should check
Teams running cym1102 nginxWebUI 3.5.0 or earlier, which expose the admin web UI and runCmd endpoint.
“nginxWebUI ≤ 3.5.0 runCmd - Remote Command Execution”
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 50 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.5.8.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- cym1102 nginxWebUI
From 3.0.0 · fixed in 3.5.8
Evidence 8
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2023-54419 |
| Record | NVD · CVE-2023-54419 |
| Public exploit code 3Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | ctfiot.com · 124166.html |
| Exploit | GitHub · qingchenhh/qc_poc · Goby/nginxWebUI_runCmd_rce.go |
| Repository | GitHub · projectdiscovery/nuclei-templates · http/vulnerabilities/other/nginxwebui-runcmd-rce.yaml |
| Other links 3 | |
| Patch | GitHub · cym1102/nginxWebUI · Commit 6b8c9bce |
| Link | vulncheck.com · advisories/nginxwebui-3.0.0-before-3.5.8-authentication-bypass-rce-via-runcmd |
| Link | vulncheck.com · advisories/nginxwebui-3.0.0-3.5.8-authentication-bypass-rce-via-runcmd |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2023-54419
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: cve.now feed data
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: github.com
Which versions are affected by CVE-2023-54419?
nginxWebUI: from 3.0.0 before 3.5.8.Source: cve.now feed data
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: github.com
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: github.com