how to fix CVE-2025-1647
-
How do we fix the vulnerability from the latest of pfsense?
It is using bootstrap 3.4.1 and reach the EOL. -
From the Googley AI.. which to me is just common sense anyways..
General Advice: To reduce risk, limit access to the pfSense WebGui to trusted networks only and minimize the use of non-essential third-party packages that might expose vulnerable frontend components.
Have you installed the "Patches" package?
-
We are using the latest 2.8.1 PFSense and found the older bootstrap javascript during vulnerability assessment.
Do we still have to patch? Any idea what are the steps to patch it to the latest bootstrap 5.0?
-
~~CVE-2025-1647 is an XSS vulnerability in Bootstrap 3.x's data-template attribute in Tooltip and Popover components. The severity in pfSense's specific context is worth understanding before deciding how to respond.
The risk in pfSense is significantly lower than the CVE score suggests for a few reasons:
- The pfSense WebGUI uses Bootstrap tooltips and popovers, but the data-template values are set by Netgate's own PHP code, not by user-supplied input in most cases
- If your WebGUI is only accessible from trusted internal networks (as it should be), the attack surface is limited to already-authenticated administrators
That said, for a vulnerability assessment the finding is legitimate since Bootstrap 3.4.1 is documented as EOL and carrying this CVE.
What you can actually do:
-
Upgrade to pfSense Plus 26.03 if you're on CE 2.8.1 and eligible. Netgate has been updating frontend dependencies in the Plus track. Check the release notes to see if Bootstrap was updated.
-
For pfSense CE: there is no supported path to manually upgrade Bootstrap without breaking the webGUI, since the templates are tightly coupled to Bootstrap 3's API. Manually replacing bootstrap.min.js with a 5.x version will break the UI.
-
Mitigation for your assessment: document that WebGUI access is restricted to trusted management networks/VLANs only. This is the standard accepted mitigation for bootstrap-in-admin-UI findings. Most security auditors accept this with a network diagram showing access controls.
-
The "Patches" package chpalmer mentioned can apply unofficial fixes, but there is no community-maintained patch specifically for CVE-2025-1647 at the moment.
If you're stuck on CE 2.8.1 with a hard requirement to remediate, the only fully clean path is migrating to pfSense Plus where Netgate controls the update cadence.
~~