CVE-2025-34314: IPFire · XSS or 'Cross-site Scripting'
Affects IPFireSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% 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:N/VI:N/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IPFire.org IPFire | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-34314, European organizations should prioritize upgrading IPFire installations to version 2.29 (Core Update 198) or later, where this vulnerability is addressed. In the absence of an official patch, administrators should restrict access to the IPFire web interface to trusted networks and users only, employing network segmentation and VPNs to limit exposure. Implement strong authentication mechanisms, such as multi-factor authentication, to reduce the risk of unauthorized access. Regularly audit and monitor time constraint rules and other user-generated content for suspicious entries that could indicate attempted exploitation. Additionally, applying Content Security Policy (CSP) headers on the IPFire web interface, if configurable, can help mitigate the impact of injected scripts. Educate administrators about the risks of XSS and encourage cautious handling of user input fields. Finally, maintain up-to-date backups of configuration data to enable rapid recovery if compromise occurs.
Description
IPFire versions prior to 2.29 (Core Update 198) contain a stored cross-site scripting (XSS) vulnerability that allows an authenticated attacker to inject arbitrary JavaScript code through the SRC, DST, and COMMENT parameters when creating a time constraint rule. When a user adds a time constraint rule the application issues an HTTP POST request to /cgi-bin/urlfilter.cgi with the MODE parameter set to TIMECONSTRAINT and the source hostnames/IPs, destination, and remark provided in the SRC, DST, and COMMENT parameters respectively. The values of these parameters are stored and later rendered in the web interface without proper sanitation or encoding, allowing injected scripts to execute in the context of other users who view the affected time constraint entry.