Vulnerability · CVE-2017-1000479
pfSense versions 2.4.1 and lower are vulnerable to clickjacking attacks in the CSRF error page resulting in privileged execution of arbitrary code, because the error d…
Published Jan 3, 2018 · catalog updated Jun 17, 2026 · the affected product
Last checked Nov 9, 2026. A connected source was read within the last 7 days.
Check this week
CVE-2017-1000479 is not in CISA KEV. FIRST estimates a 31.70% chance of exploitation in the next 30 days. Check whether you run the affected product.
Gaps on this record
- No plain product name is stored. The page cannot tell you which product to check.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-111232 · Medium
- CVE-2026-111227 · Medium
- CVE-2026-111222 · High
- CVE-2026-111221 · High
- CVE-2026-111219 · High
- Severity
- High8.8
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 31.70%
- Remediation
- Version ranges on file
- Affected products
- cpe netgate/pfsense · cpe opnsense project/opnsense
pfSense versions 2.4.1 and lower are vulnerable to clickjacking attacks in the CSRF error page resulting in privileged execution of arbitrary code, because the error detection occurs before an X-Frame-Options header is set. This is fixed in 2.4.2-RELEASE. OPNsense, a 2015 fork of pfSense, was not vulnerable since version 16.1.16 released on June 06, 2016. The unprotected web form was removed from the code during an internal security audit under "possibly insecure" suspicions.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe netgate/pfsense<= 2.4.1
- cpe opnsense project/opnsense< 16.1.16
How to fix CVE-2017-1000479
Upgrade
CVE-2017-1000479 lists a fix boundary at 2.4.1. Compare the installed build with that boundary before you change production.
Version check
Affected <= 2.4.1
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2017-1000479 is not in CISA KEV. FIRST estimates a 31.70% chance of exploitation in the next 30 days. Check whether you run the affected product.
Which versions are affected?
Compare what you have installed with opnsense project/opnsense < 16.1.16. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-352: Cross-Site Request Forgery (CSRF). EPSS 31.70%. There is no CISA KEV listing. A public exploit reference is linked in Sources. That is not the same as confirmed exploitation. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Jan 3, 2018 · Monitored products — high
Detected
pfSense versions 2.4.1 and lower are vulnerable to clickjacking attacks in the CSRF error page resulting in privileged execution of arbitrary code, because the error detection occurs before an X-Frame-Options header is set. This is fixed in 2.4.2-RELEASE. OPNsense, a 2015 fork of pfSense, was not vulnerable since version 16.1.16 released on June 06, 2016. The unprotected web form was removed from
Jun 17, 2026 · Monitored products — high
Updated
pfSense versions 2.4.1 and lower are vulnerable to clickjacking attacks in the CSRF error page resulting in privileged execution of arbitrary code, because the error detection occurs before an X-Frame-Options header is set. This is fixed in 2.4.2-RELEASE. OPNsense, a 2015 fork of pfSense, was not vulnerable since version 16.1.16 released on June 06, 2016. The unprotected web form was removed from
Sources
- CVE.orgVulnerability recordCVE-2017-1000479
Official CVE identifier
cve.org - Monitored products — highVendor advisoryCVE-2017-1000479
pfSense versions 2.4.1 and lower are vulnerable to clickjacking attacks in the CSRF error page resulting in privileged execution of arbitrary code, because the error detection occurs before an X-Frame-Options header is set. This is fixed in 2.4.2-RELEASE. OPNsense, a 2015 fork of pfSense, was not vulnerable since version 16.1.16 released on June 06, 2016. The unprotected web form was removed from
nvd.nist.gov - Metasploit ModulesPublic exploit moduleexploit_unix/http/pfsense_clickjacking
Public module reference (normal). Module source is not copied into this catalog.
rapid7.com
References
Freshness
Last verified in this catalog Nov 9, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- Metasploit ModulesNov 7, 2026
- CVE.orgNov 6, 2026
- Monitored products — highNov 6, 2026