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

> Attackers can write arbitrary files via the Import Certificate feature, potentially achieving remote code execution by overwriting configuration files.

- **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:** Yes
- **Published:** 29 Jan 2024
- **Updated:** 12 Nov 2024
- **Also known as:** GHSA-xvq9-4vpv-227m, GO-2024-2481

## What is CVE-2024-23827?

CVE-2024-23827 is a critical path traversal vulnerability in 0xJacky nginx-ui, published on 29 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

3 open source packages ship an affected version, including github.com/0xJacky/Nginx-UI. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/0xJacky/Nginx-UI` | Go | All versions | None |
| `github.com/0xJacky/Nginx-UI` | Go | All versions | 1.9.10-0.20240128060047-8581bdd3c6f4 |
| `github.com/0xJacky/Nginx-UI` | Go | All versions | 1.9.10-0.20240128060047-8581bdd3c6f4 |

Products: Nginxui Nginx Ui.

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

Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20240128060047-8581bdd3c6f4 or later.

## Is CVE-2024-23827 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-23827 exists.

## Other vulnerabilities in 0xJacky nginx-ui

- [CVE-2026-33032](https://insights.sbomify.com/CVE-2026-33032/): Nginx UI: Unauthenticated MCP Endpoint Allows Remote Nginx Takeover (critical 9.8)
- [CVE-2026-27944](https://insights.sbomify.com/CVE-2026-27944/): Nginx UI: Unauthenticated Backup Download with Encryption Key Disclosure (critical 9.8)
- [CVE-2026-107806](https://insights.sbomify.com/CVE-2026-107806/): Nginx UI: Authenticated Remote Code Execution via Backup Restore App Config Overwrite (critical 9.4)
- [CVE-2026-33026](https://insights.sbomify.com/CVE-2026-33026/): nginx-ui Backup Restore Allows Tampering with Encrypted Backups (critical 9.4)
- [CVE-2026-42238](https://insights.sbomify.com/CVE-2026-42238/): Unauthenticated Remote Code Execution via Backup Restore in nginx-ui (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-23827 is a critical path traversal vulnerability in 0xJacky nginx-ui, published on 29 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-23827 exists.

Affected packages and fixed versions:
- github.com/0xJacky/Nginx-UI (Go): affected all versions; no fix listed
- github.com/0xJacky/Nginx-UI (Go): affected all versions; fixed in 1.9.10-0.20240128060047-8581bdd3c6f4
- github.com/0xJacky/Nginx-UI (Go): affected all versions; fixed in 1.9.10-0.20240128060047-8581bdd3c6f4

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-23827/ (Markdown: https://insights.sbomify.com/CVE-2024-23827/index.md)
```

## Sources

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

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