Threat database

Nginx Proxy Manager versions up to 2.16.0 contain an authorization flaw that allows non-administrator users with manage permissions to inject arbitrary nginx directives via the advanced_config field. This improper restriction can enable attackers to manipulate nginx configurations, such as serving arbitrary files or controlling routing for their assigned hosts.

Nginx Proxy Manager versions up to 2.16.0 have a critical vulnerability due to lack of rate-limiting on authentication endpoints. This allows unauthenticated attackers to perform unlimited password guessing attacks and brute-force two-factor authentication codes, potentially gaining full administrative access.

A vulnerability was detected in NginxProxyManager nginx-proxy-manager up to 2.15.1. This impacts the function internalCertificate.validate of the file backend/internal/certificate.js of the component Validate Route. The manipulation results in missing authentication. The attack can be launched remotely. The exploit is now public and may be used. Endpoint only processes and echoes back the certificate the caller submits (no stored data leaked); the real risk is unauthenticated openssl processing of attacker input. The project was informed of the problem early through an issue report but has not responded yet.

Nginx Proxy Manager versions 2.9.14 through 2.15.1, fixed in commit a5db5ed, contain an authenticated remote code execution vulnerability via OS command injection in the setupCertbotPlugins() function in backend/setup.js, allowing attackers with certificates:manage permission to execute arbitrary commands by storing a malicious payload in the dns_provider_credentials field. The user-controlled dns_provider_credentials value is interpolated directly into a shell command executed via child_process.exec() without sanitization or escaping, causing the injected command to execute upon backend restart.