CVE-2025-34174: Netgate pfSense CE · XSS or 'Cross-site Scripting'
Affects Netgate pfSense CESource CVE Database V5
Not known to be exploited · 14% EPSS · CVSS 5.1 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 14.4% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N/SC:L/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Netgate pfSense CE | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-34174, organizations should first restrict access to the pfSense web interface to trusted administrators only, using network segmentation, VPNs, or IP whitelisting to reduce exposure. Review and minimize the number of users granted 'WebCfg - Status: Traffic Totals' permissions to limit potential attackers. Implement strict input validation and output encoding on the 'start-day' parameter in the pfSense web interface, either by applying vendor patches when available or by manually sanitizing inputs if feasible. Monitor web interface logs for suspicious input patterns or unusual user activity. Educate administrators about the risks of stored XSS and encourage cautious behavior when interacting with the Status Traffic Totals page. Consider upgrading pfSense to a later version if a patch addressing this vulnerability is released. In the interim, disable or restrict access to the Status Traffic Totals page if possible. Employ web application firewalls (WAFs) or intrusion detection systems (IDS) that can detect and block XSS payloads targeting the pfSense interface. Regularly audit user permissions and conduct vulnerability assessments to detect similar issues.
Description
In pfSense CE /usr/local/www/status_traffic_totals.php, the value of the start-day parameter is not ensured to be a numeric value or sanitized of HTML-related characters/strings before being directly displayed in the input box. This value can be saved as the default value to be displayed to all users when visiting the Status Traffic Totals page, resulting in stored cross-site scripting. The attacker must be authenticated with at least "WebCfg - Status: Traffic Totals" permissions.