Nginx-UI AuthRequired token cookie fallback enables CSRF against management APIs

Why it is Amber

• CVSS 8.8 high
• Public exploit or proof of concept referenced
• Remotely exploitable without logging in
• On your watchlist: nginx, Go

Affected packages

References

• https://github.com/advisories/GHSA-33rr-wq23-g6gg
• https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-33rr-wq23-g6gg
• https://github.com/0xJacky/nginx-ui/commit/a3999bd78a3b97ab22e6b5e9fd478ac57598a954
• https://github.com/0xJacky/nginx-ui/releases/tag/v2.5.0
• https://github.com/advisories/GHSA-33rr-wq23-g6gg

Original description

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.