CSRF in 0xjacky Nginx-Ui
CVE-2026-107809
Nginx UI is a web user interface for the Nginx web server. From 2.0.0 until 2.5.0, AuthRequired accepts a browser-managed token cookie as an API credential after the front end stores the JWT in that cookie. Because management endpoints do not universally require a CSRF token or perform Origin or Referer validation, a remote attacker can induce a logged-in administrator's browser to submit authenticated cross-site state-changing requests, including POST /api/configs. The attack requires an administrator account without OTP/Passkey or a target endpoint that does not require secure-session proof. The attacker cannot read the cross-origin response but can modify Nginx configuration, trigger reloads, or invoke other management operations reachable with the victim's session. This issue is fixed in version 2.5.0.
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- 0xjacky Nginx-Ui — versions >= 2.0.0, < 2.5.0
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-107809?
- CVE-2026-107809 is a high-severity vulnerability in 0xjacky Nginx-Ui, classified under Cross-Site Request Forgery (CSRF). CVSS score: 8.8/10. Published 2026-10-09.
- How severe is CVE-2026-107809?
- High severity. CVSS v3 base score is 8.8 out of 10.