IPFire versions prior to 2.29 (Core Update 198) contain a stored cross-site scripting (XSS) vulnerability that allows
Source GCVE Database
Not known to be exploited · CVSS 5.1 Medium · fixed in 2.29 : update web interface. IPFire when convenient.
Data as of 29 Oct 2026, 23:58 UTC
- Affects
- web interface. IPFire prior to 2.29
- 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
Weaponized: 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 29 Oct 2026.
What to do
AI-suggested
If you cannot patch yet, restrict access to the whitelist management interface to trusted users only and consider monitoring for suspicious activity related to whitelist entries.
Description
IPFire versions prior to 2.29 (Core Update 198) have a stored cross-site scripting (XSS) vulnerability. This flaw allows an authenticated attacker to inject arbitrary JavaScript code via the IGNORE_ENTRY_REMARK parameter when adding a whitelisted host. The injected script is stored and later executed in the context of other users viewing the whitelist entry in the web interface.