Nginx UI OTP secure-session step-up is missing on sensitive mutation routes

[ 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, Nginx UI does not apply RequireSecureSession to multiple authenticated mutation routes even though OTP-enabled users are expected to present a fresh X-Secure-Session-ID for sensitive actions. A stolen authenticated session can therefore create or alter automatic backups, DNS credentials and records, certificates and ACME users, Nginx control settings, and site or stream automation without completing the OTP or passkey step-up. This issue is fixed in version 2.4.1.

[ Fixes ]Fixes and patches

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

[ Packages ]Affected open-source packages

• github.com/0xJacky/Nginx-UI goAffected < 1.9.10-0.20260703131214-23d1934099b0 · fixed in 1.9.10-0.20260703131214-23d1934099b0 · GHSA-5v7c-xpfp-p65m

[ 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-5v7c-xpfp-p65m