NVD / CVE Program· CNA GitHub_M

CVE-2024-23827: Nginx-UI arbitrary file write through the Import Certificate feature

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 39/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.70% (FIRST EPSS); higher than 53.7% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: github.com/0xJacky/Nginx-UI (Go) 1.9.10-0.20240128060047-8581bdd3c6f4.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to github.com/0xJacky/Nginx-UI (Go) 1.9.10-0.20240128060047-8581bdd3c6f4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Nginx-UI is a web interface to manage Nginx configurations. The Import Certificate feature allows arbitrary write into the system. The feature does not check if the provided user input is a certification/key and allows to write into arbitrary paths in the system. It's possible to leverage the vulnerability into a remote code execution overwriting the config file app.ini. Version 2.0.0.beta.12 fixed the issue.

Published: Jan 29, 2024
Updated: Jun 17, 2026
EPSS: 0.7% · 53th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.7%

CISA SSVC decision

Exploitation: proof of concept
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 9.8
CNA · GitHub_M: 9.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
nginxui	nginx ui	cpe:2.3:a:nginxui:nginx_ui

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

0xJacky nginx-ui
- < 2.0.0.beta.12affected

Affected versions · NVD (20)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

nginxui nginx ui1.2.0
nginxui nginx ui1.2.1
nginxui nginx ui1.2.2
nginxui nginx ui1.3.0
nginxui nginx ui1.3.1
nginxui nginx ui1.3.2
nginxui nginx ui1.3.3
nginxui nginx ui1.4.0
nginxui nginx ui1.4.1
nginxui nginx ui1.4.2
nginxui nginx ui1.5.0
nginxui nginx ui1.5.1
nginxui nginx ui1.5.2
nginxui nginx ui1.6.0
nginxui nginx ui1.6.1
nginxui nginx ui1.6.2
nginxui nginx ui1.6.3
nginxui nginx ui1.6.5
nginxui nginx ui1.6.6
nginxui nginx ui1.6.7

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	github.com/0xJacky/Nginx-UI	from 0	—
Go	github.com/0xJacky/Nginx-UI	before 1.9.10-0.20240128060047-8581bdd3c6f4	1.9.10-0.20240128060047-8581bdd3c6f4

Same product

nginxui: all records

Other highest-scoring records for the same primary product.

CVE-2026-33032Nginx UI: Unauthenticated MCP Endpoint Allows Remote Nginx Takeover
50Plan
CVE-2026-27944Nginx UI: Unauthenticated Backup Download with Encryption Key Disclosure
46Plan
CVE-2024-49368Unchecked logrotate settings lead to arbitrary command execution
43Plan

Published before and after this one in the same product

← EarlierCVE-2024-22196Jan 11, 2024 · Authenticated (user role) SQL injection in `OrderAndPaginate` (GHSL-2023-270)
26Monitor
← EarlierCVE-2024-22198Jan 11, 2024 · Authenticated (user role) arbitrary command execution by modifying `start_cmd` setting (GHSL-2023-268)
36Monitor
Later →CVE-2024-23828Jan 29, 2024 · Nginx-UI authenticated RCE through injecting into the application config via CRLF
35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Go:github.com/0xJacky/Nginx-UI	1.9.10-0.20240128060047-8581bdd3c6f4	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2024-49366266 days apartNginx UI's json field can construct a directory traversal payload, causing arbitrary files to be written
30Monitor

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-0074 · Jan 30, 2024(NGINX Güvenlik Zafiyeti)

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/0xJacky/nginx-ui/security/advisories/GHSA-xvq9-4vpv-227m

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records