pfsense

11 records · 11 with a public proof-of-concept

Disclosed vulnerabilities where the NVD names pfsense as an affected vendor, highest CVSS first.

  1. HIGH 7.2CVE-2026-111231public PoC

    Netgate pfSense CE through 2.9.0 contains an authorization bypass vulnerability that allows read-only WebGUI users to replace config.xml because config_restore() and config_install() ignore the 'User - Config: Deny Config Write' privilege. Attackers holding pa…

    pfsense

    AI risk analysis on Exploit-DB.ai →

  2. HIGH 7.2CVE-2026-111223public PoC

    Netgate pfSense CE 2.7.0 through 2.9.0 contains a configuration injection vulnerability that allows authenticated users with IPsec Mobile privileges to execute commands as root via the login_banner field. Attackers can submit a single-line banner containing '}…

    pfsense

    AI risk analysis on Exploit-DB.ai →

  3. HIGH 7.2CVE-2026-111216public PoC

    Netgate pfSense CE through 2.9.0 contains an OS command injection vulnerability that allows authenticated users with gateway edit privileges to execute commands as root by injecting shell metacharacters into an IPv6 link-local zone index. Attackers can set a g…

    pfsense

    AI risk analysis on Exploit-DB.ai →

  4. HIGH 7.2CVE-2026-111215public PoC

    Netgate pfSense CE through 2.9.0 contains an OS command injection vulnerability that allows authenticated users to execute commands as root by supplying a crafted wireless parent interface name. Attackers with limited Wireless Edit or Interface Assignments pri…

    pfsense

    AI risk analysis on Exploit-DB.ai →

  5. HIGH 7.2CVE-2026-111214public PoC

    Netgate pfSense CE 2.7.0 through 2.9.0 contains an OS command injection vulnerability that allows authenticated users with QinQ edit privilege to run commands by storing an unvalidated parent interface name. Attackers can save a crafted 'if' value, then edit t…

    pfsense

    AI risk analysis on Exploit-DB.ai →

  6. MEDIUM 5.5CVE-2026-111228public PoC

    Netgate pfSense CE from 2.7.1 through 2.9.0 contains a CRLF injection vulnerability in services_unbound_advanced.php that allows authenticated users with DNS Resolver: Advanced privilege to inject Unbound directives. Attackers can embed CR/LF characters in the…

    pfsense

    AI risk analysis on Exploit-DB.ai →

  7. MEDIUM 5.5CVE-2026-111227public PoC

    Netgate pfSense CE through 2.9.0 contains a CRLF injection vulnerability in services_unbound_acls.php that allows authenticated users with the DNS Resolver: Access Lists privilege to inject Unbound configuration directives. Attackers can embed CR/LF characters…

    pfsense

    AI risk analysis on Exploit-DB.ai →

  8. MEDIUM 5CVE-2026-111225public PoC

    Netgate pfSense CE 2.5.0 through 2.9.0 contains an OS command injection vulnerability in openvpn.learn-address.sh that allows authenticated VPN clients to execute commands as the unbound user. Attackers can embed shell metacharacters in the certificate common …

    pfsense

    AI risk analysis on Exploit-DB.ai →

  9. MEDIUM 4.9CVE-2026-111230public PoC

    Netgate pfSense CE through 2.9.0 contains a local file read vulnerability that allows users with the Dynamic DNS client privilege to read files as root by setting a file:// custom Update URL in services_dyndns_edit.php. Attackers can set a non-matching Result …

    pfsense

    AI risk analysis on Exploit-DB.ai →

  10. MEDIUM 4.8CVE-2026-111232public PoC

    Netgate pfSense CE 2.3.0 through 2.9.0 contains a stored cross-site scripting vulnerability that allows authenticated users with Firewall: Rules or NAT: Port Forward privileges to inject scripts via the separator color field. Attackers can submit a crafted sep…

    pfsense

    AI risk analysis on Exploit-DB.ai →

  11. MEDIUM 4.7CVE-2026-111233public PoC

    Netgate pfSense CE 2.7.1 through 2.9.0 contains a reflected cross-site scripting vulnerability in firewall_rules.php that allows remote attackers to inject script via the unencoded if parameter. When the non-default Require Firewall Interface option is enabled…

    pfsense

    AI risk analysis on Exploit-DB.ai →