CVE-2025-34306 [Medium] | XSS in Ipfire

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 pienumber parameter when updating the default firewall IP search values. When a user updates these defaults, the application issues an HTTP POST request to /cgi-bin/logs.cgi/firewalllogip.dat with the default number of IPs in the pienumber 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 page.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-10-29	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-10-29

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.1	4.0	MEDIUM	`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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network. Attack complexity (AC:L) Exploitation conditions are straightforward and stable. Attack requirements (AT:N) No additional preconditions are required beyond normal reachability. Privileges required (PR:L) Low privileges are required. User interaction (UI:P) A user has to participate (for example click/open/approve). Vulnerable system confidentiality impact (VC:N) No confidentiality impact on the vulnerable system. Vulnerable system integrity impact (VI:N) No integrity impact on the vulnerable system. Vulnerable system availability impact (VA:N) No availability impact on the vulnerable system. Subsequent system confidentiality impact (SC:L) Limited confidentiality impact on subsequent systems. Subsequent system integrity impact (SI:L) Limited integrity impact on subsequent systems. Subsequent system availability impact (SA:N) No availability impact on subsequent systems. Exploit maturity (threat) (E:X) Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked). Confidentiality requirement (CR:X) Not defined: insufficient information; scoring treats this like High (worst case). Integrity requirement (IR:X) Not defined: insufficient information; scoring treats this like High (worst case). Availability requirement (AR:X) Not defined: insufficient information; scoring treats this like High (worst case). Modified attack vector (MAV:X) Not defined: scoring uses the Base Attack Vector (AV). Modified attack complexity (MAC:X) Not defined: scoring uses the Base Attack Complexity (AC). Modified attack requirements (MAT:X) Not defined: scoring uses the Base Attack Requirements (AT). Modified privileges required (MPR:X) Not defined: scoring uses the Base Privileges Required (PR). Modified user interaction (MUI:X) Not defined: scoring uses the Base User Interaction (UI). Modified vulnerable system confidentiality impact (MVC:X) Not defined: scoring uses the Base VC metric. Modified vulnerable system integrity impact (MVI:X) Not defined: scoring uses the Base VI metric. Modified vulnerable system availability impact (MVA:X) Not defined: scoring uses the Base VA metric. Modified subsequent system confidentiality impact (MSC:X) Not defined: scoring uses the Base SC metric. Modified subsequent system integrity impact (MSI:X) Not defined: scoring uses the Base SI metric. Modified subsequent system availability impact (MSA:X) Not defined: scoring uses the Base SA metric. Safety (supplemental) (S:X) Not evaluated. Automatable (supplemental) (AU:X) Not evaluated. Recovery (supplemental) (R:X) Not evaluated. Value density (supplemental) (V:X) Not evaluated. Vulnerability response effort (supplemental) (RE:X) Not evaluated. Provider urgency (supplemental) (U:X) Not evaluated.	—	—	[email protected]
5.4	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	2.3	2.7	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.1

4.0

MEDIUM

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network.
Attack complexity (AC:L): Exploitation conditions are straightforward and stable.
Attack requirements (AT:N): No additional preconditions are required beyond normal reachability.
Privileges required (PR:L): Low privileges are required.
User interaction (UI:P): A user has to participate (for example click/open/approve).
Vulnerable system confidentiality impact (VC:N): No confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:N): No integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:N): No availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:L): Limited confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:L): Limited integrity impact on subsequent systems.
Subsequent system availability impact (SA:N): No availability impact on subsequent systems.
Exploit maturity (threat) (E:X): Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X): Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X): Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X): Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X): Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X): Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X): Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X): Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X): Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X): Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X): Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X): Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X): Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X): Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X): Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X): Not evaluated.
Automatable (supplemental) (AU:X): Not evaluated.
Recovery (supplemental) (R:X): Not evaluated.
Value density (supplemental) (V:X): Not evaluated.
Vulnerability response effort (supplemental) (RE:X): Not evaluated.
Provider urgency (supplemental) (U:X): Not evaluated.

—

[email protected]

5.4

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

2.3

2.7

[email protected]

Affected software / configurations for CVE-2025-34306

Vendor	Product	Version	Raw CPE
ipfire	ipfire	< 2.29	cpe:2.3:a:ipfire:ipfire::::::::
ipfire	ipfire	2.29	cpe:2.3:a:ipfire:ipfire:2.29:core_update183::::::
ipfire	ipfire	2.29	cpe:2.3:a:ipfire:ipfire:2.29:core_update184::::::
ipfire	ipfire	2.29	cpe:2.3:a:ipfire:ipfire:2.29:core_update185::::::
ipfire	ipfire	2.29	cpe:2.3:a:ipfire:ipfire:2.29:core_update186::::::
ipfire	ipfire	2.29	cpe:2.3:a:ipfire:ipfire:2.29:core_update187::::::
ipfire	ipfire	2.29	cpe:2.3:a:ipfire:ipfire:2.29:core_update188::::::
ipfire	ipfire	2.29	cpe:2.3:a:ipfire:ipfire:2.29:core_update189::::::
ipfire	ipfire	2.29	cpe:2.3:a:ipfire:ipfire:2.29:core_update190::::::
ipfire	ipfire	2.29	cpe:2.3:a:ipfire:ipfire:2.29:core_update191::::::
ipfire	ipfire	2.29	cpe:2.3:a:ipfire:ipfire:2.29:core_update192::::::
ipfire	ipfire	2.29	cpe:2.3:a:ipfire:ipfire:2.29:core_update193::::::
ipfire	ipfire	2.29	cpe:2.3:a:ipfire:ipfire:2.29:core_update194::::::
ipfire	ipfire	2.29	cpe:2.3:a:ipfire:ipfire:2.29:core_update195::::::
ipfire	ipfire	2.29	cpe:2.3:a:ipfire:ipfire:2.29:core_update196::::::
ipfire	ipfire	2.29	cpe:2.3:a:ipfire:ipfire:2.29:core_update197::::::

References for CVE-2025-34306

URL	Tags
https://bugzilla.ipfire.org/show_bug.cgi?id=13881	Issue Tracking Third Party Advisory
https://www.ipfire.org/blog/ipfire-2-29-core-update-198-released	Release Notes
https://www.vulncheck.com/advisories/ipfire-stored-xss-via-default-ip-search-value	Third Party Advisory

URL

CVE-2025-34306 | IPFire < v2.29 Stored XSS via Default IP Search Value

Exploit prediction scoring system (EPSS) score for CVE-2025-34306

Common vulnerability scoring system (CVSS) metrics for CVE-2025-34306

Weakness enumeration for CVE-2025-34306

Affected software / configurations for CVE-2025-34306

References for CVE-2025-34306