Skip to main content
Mallory
UnratedVulnerability

CVE-2019-12462: Cross-site scripting in pfSense WebGUI legacy AutoConfigBackup settings

Updated 28 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2019-12462CWE-79

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

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.
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.