Loading vulnerability…
pfSense versions 2.4.1 and earlier are vulnerable to clickjacking attacks on the CSRF error page. The vulnerability arises because the error detection logic is executed before the X-Frame-Options header is set, allowing the page to be embedded in a malicious frame. This can result in privileged execution of arbitrary code if an attacker tricks an authenticated user into interacting with a maliciously framed page. OPNsense, a fork of pfSense, removed the vulnerable code in version 16.1.16.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/unix/http/pfsense_clickjacking.rb) that exploits a clickjacking vulnerability (CVE-2017-1000479) in pfSense <= 2.4.1. The exploit works by serving a malicious HTML page that tricks an authenticated pfSense admin into submitting a hidden form to the diag_command.php endpoint, resulting in the execution of arbitrary PHP code as root. The module leverages Metasploit's payload system to inject the attacker's code. The attack vector is browser-based social engineering, requiring the victim to be logged into the pfSense WebGUI and to visit the attacker's page. The code references static resources (JS, CSS, image) for the malicious page, and the main endpoints involved are the pfSense WebGUI (defaulting to https://192.168.1.1) and the diag_command.php script. The exploit is operational and can lead to full system compromise if successful.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.