0xJacky Nginx UI up to 2.4.x Authentication /api/configs AuthRequired cross-site request forgery

Summaryinfo

A vulnerability identified as problematic has been detected in 0xJacky Nginx UI up to 2.4.x. The affected element is the function AuthRequired of the file /api/configs of the component Authentication. The manipulation leads to cross-site request forgery. This vulnerability is traded as CVE-2026-107809. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in 0xJacky Nginx UI up to 2.4.x and classified as problematic. This issue affects the function AuthRequired of the file /api/configs of the component Authentication. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is integrity. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-107809 since 10/08/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

Upgrading to version 2.5.0 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-95892). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Web Server

Vendor

• 0xJacky

Name

• Nginx UI

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion