Skip to main content
VulnerabilityPublished Updated

CVE-2024-46256: nginx-proxy-manager · A Command Injection

Affects nginx-proxy-managerSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
3.0% chance of exploitation in 30 days – higher than 87% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Sep 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubnginxproxymanager/nginx-proxy-managerpkg:github/nginxproxymanager/nginx-proxy-managerOther threatsAffected
  • =2.11.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately assess their exposure to NginxProxyManager version 2.11.3 and restrict network access to the management interface, ideally limiting it to trusted IP addresses or VPNs. Until an official patch is released, consider disabling the Add Let's Encrypt Certificate functionality if feasible or implementing strict input validation and sanitization at the application or proxy level to block malicious payloads. Monitor logs for unusual command execution attempts or anomalies in SSL certificate requests. Employ network intrusion detection/prevention systems (IDS/IPS) with updated signatures to detect exploitation attempts. Regularly back up configurations and data to enable recovery in case of compromise. Stay informed about vendor advisories and apply patches promptly once available. Additionally, conduct internal penetration testing to verify the absence of exploitable command injection vectors in customized deployments. Implementing application-layer firewalls or web application firewalls (WAFs) with custom rules targeting command injection patterns can provide an additional layer of defense.

Description

A Command injection vulnerability in requestLetsEncryptSsl in NginxProxyManager 2.11.3 allows an attacker to RCE via Add Let's Encrypt Certificate.

References

Community reviews

Loading reviews…