Skip to main content
VulnerabilityPublished Updated

CVE-2025-34310: IPFire · XSS or 'Cross-site Scripting'

Affects IPFireSource CVE Database V5

0

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
IPFire.org IPFireAffected
  • =0
Fixed in–

AI-suggested

  1. Upgrade IPFire installations to version 2.29 (Core Update 198) or later, where this vulnerability is fixed.
  2. If immediate upgrade is not possible, restrict access to the IPFire web interface to trusted networks and users only, minimizing exposure to authenticated attackers.
  3. Enforce strong authentication mechanisms and regularly audit user accounts to prevent unauthorized access.
  4. Implement web application firewall (WAF) rules to detect and block suspicious POST requests targeting the QoS parameters (INC_SPD, OUT_SPD, DEFCLASS_INC, DEFCLASS_OUT).
  5. Educate administrators to avoid clicking on suspicious links or performing QoS updates from untrusted devices.
  6. Monitor logs for unusual QoS configuration changes or repeated POST requests to /cgi-bin/qos.cgi.
  7. Consider isolating the management interface from general user networks to reduce risk of cross-site scripting impact.
  8. Apply Content Security Policy (CSP) headers if configurable in IPFire to limit script execution origins. These targeted steps go beyond generic advice by focusing on access control, monitoring, and specific parameter filtering relevant 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 INC_SPD, OUT_SPD, DEFCLASS_INC, and DEFCLASS_OUT parameters when updating Quality of Service (QoS) settings. When a user updates speeds or classes, the application issues an HTTP POST request to /cgi-bin/qos.cgi and the values for incoming/outgoing speeds and default classes are provided in the INC_SPD, OUT_SPD, DEFCLASS_INC, and DEFCLASS_OUT parameters. 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 QoS entries.

References

Community reviews

Loading reviews…