Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-84314)
Summary
Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-84314). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/users/. Mitigation: upgrade to 1.9.10-0.20260703131214-23d1934099b0 or later.
Original description
The description as published by the source.
Summary
POST /api/users/:id allows any authenticated user to change any other user's password without RequireSecureSession (2FA verification). In contrast, the self password change endpoint POST /api/user/password correctly requires RequireSecureSession. This inconsistency enables any authenticated user to take over the initial admin account (user ID 1) by simply changing its password.
Details
nginx-ui enforces RequireSecureSession middleware on sensitive operations such as self password change (api/user/router.go:55), self profile update (api/user/router.go:54), settings modification (api/settings/router.go:12), and config file deletion/rename (api/config/router.go:16-21).
However, the user management endpoint registered in InitManageUserRouter (api/user/user.go:31-68) is mounted on the g router group (router/routers.go:92) which only applies middleware.AuthRequired() and middleware.Proxy() — no RequireSecureSession().
As a result, POST /api/users/:id with a password field in the JSON body updates the target user's password with only basic JWT authentication. No 2FA or secure session verification is performed, even if the target user has 2FA enabled.
The attack flow:
- Attacker authenticates as any user (e.g., user ID 2).
- Attacker sends
POST /api/users/1with{"password": "attacker-chosen"}. - Admin (user ID 1) password is changed. All existing admin tokens are invalidated (
api/user/user.go:48-49). - Attacker l…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-84314 has been found in github.com/0xJacky/Nginx-UI.
Attackers can target a specific entry point like POST /api/users/ over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260703131214-23d1934099b0 or later.
If unsure, ask your IT team or search "github.com/0xJacky/Nginx-UI CVE-2026-84314" on the vendor's site.
CVE-2026-84314 (github.com/0xJacky/Nginx-UI) — CWE-285
Attack surface: POST /api/users/ / POST /api/user/password / POST /api/users/1 / RequireSecureSession
Patched: 1.9.10-0.20260703131214-23d1934099b0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-285) exists in github.com/0xJacky/Nginx-UI. Attackers reach the vulnerable code path via POST /api/users/.
Check the vendor advisory for the affected versions of github.com/0xJacky/Nginx-UI. Attack surface: POST /api/users/ / POST /api/user/password / POST /api/users/1 / RequireSecureSession.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.9.10-0.20260703131214-23d1934099b0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/users/ requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/0xJacky/Nginx-UI' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/0xJacky/Nginx-UI' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/0xJacky/Nginx-UIを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/users/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/users/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260703131214-23d1934099b0ステージング環境で 1.9.10-0.20260703131214-23d1934099b0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/users/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com