Nginx UI: TOTP / passkey enrolment requires no re-authentication, enabling persistent account takeover

[ Why it matters ]Priority signals

• Public proof-of-concept exploit exists (CISA SSVC)

[ Description ]Official description

Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.1, POST /api/otp_enroll and POST /api/finish_passkey_register are registered outside RequireSecureSession and accept a normal authenticated session without verifying the current password. An attacker with a stolen JWT can bind an attacker-controlled TOTP secret when the victim has not already enabled TOTP, or can register an attacker-controlled passkey because that path has no equivalent existing-enrollment guard. These changes create persistent account access that can survive a password change and interfere with the legitimate user's authentication. This issue is fixed in version 2.4.1.

[ Fixes ]Fixes and patches

• Nginx-UI 1.9.10-0.20260703131214-23d1934099b0Fixed version · GitHub Advisories · go package Nginx-UI: upgrade to 1.9.10-0.20260703131214-23d1934099b0 or later (affected < 1.9.10-0.20260703131214-23d1934099b0)

[ Packages ]Affected open-source packages

• Nginx-UI goAffected < 1.9.10-0.20260703131214-23d1934099b0 · fixed in 1.9.10-0.20260703131214-23d1934099b0 · GHSA-gfrc-g87h-7h5w

[ References ]References

• github.com/0xJacky/nginx-ui/commit/23d1934099b05b2a01589b48129dc3d3159d91c2
• github.com/0xJacky/nginx-ui/releases/tag/v2.4.1
• github.com/0xJacky/nginx-ui/security/advisories/GHSA-gfrc-g87h-7h5w