CVE-2019-12462: Cross-site scripting in pfSense WebGUI legacy AutoConfigBackup settings
A cross-site scripting vulnerability in the pfSense WebGUI affects version 2.4.4-p3 and earlier. The AutoConfigBackup page includes the hostname parameter associated with legacy settings in its output without proper encoding. An attacker who can influence that parameter may cause arbitrary JavaScript to execute in the browser of a user viewing the affected page.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows arbitrary JavaScript execution in the victim's browser within the pfSense WebGUI origin, potentially compromising the user's session cookie or other session information.
Mitigation
If you can’t patch tonight, do this now.
Disable Legacy settings in AutoConfigBackup; the legacy backend has been deprecated and removed. On older releases, restrict affected pages to trusted administrators, avoid granting firewall administrators access to functions that permit arbitrary file writes, and use a dedicated browser for firewall administration rather than one used for general browsing.
Remediation
Patch, then assume compromise.
Upgrade to pfSense 2.4.5 or later using the web interface or console. Alternatively, installations running pfSense 2.4.4-p3 can apply the relevant correction through the System Patches package. The correction was committed to the development and 2.4.5 release branches on June 13, 2019.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2019-12462 exploited in the wild?
- As of Oct 25, 2026, Mallory has no reports of CVE-2019-12462 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2019-12462?
- As of Oct 25, 2026, Mallory has found no public exploit for CVE-2019-12462.
- Is there a patch for CVE-2019-12462?
- Upgrade to pfSense 2.4.5 or later using the web interface or console. Alternatively, installations running pfSense 2.4.4-p3 can apply the relevant correction through the System Patches package.
Recent activity
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.