CVE-2025-34317: IPFire · XSS or 'Cross-site Scripting'
Affects IPFireSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to 2.29 when convenient.
Data as of 26 Oct 2026, 17:16 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.
- Patch
- Available – fixed in 2.29
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
Upgrade ipfire/ipfire to 2.29.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ipfireipfire/ipfirepkg:rpm/ipfire/ipfireOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations should immediately upgrade IPFire installations to version 2.29 (Core Update 198) or later where the vulnerability is patched. If immediate patching is not feasible, restrict access to the DNS management interface to trusted administrators only, preferably via VPN or secure management networks. Implement strict input validation and output encoding on all web interface parameters, especially TLS_HOSTNAME, to prevent script injection. Enable multi-factor authentication (MFA) for all administrative accounts to reduce the risk of credential compromise. Monitor web interface logs and DNS configuration changes for suspicious activity indicative of exploitation attempts. Conduct regular security awareness training for administrators to recognize phishing or social engineering that could lead to credential theft. Consider deploying web application firewalls (WAFs) that can detect and block XSS payloads targeting the IPFire interface. Finally, maintain an incident response plan to quickly address any signs of compromise related to this vulnerability.
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 TLS_HOSTNAME parameter when adding a new DNS entry. When a user adds a DNS entry, the application issues an HTTP POST request to /cgi-bin/dns.cgi and the TLS hostname is provided in the TLS_HOSTNAME parameter. The value of this parameter is 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 DNS configuration.