CVE-2025-34317 | IPFire < v2.29 Stored XSS via DNS Creation (dns.cgi)

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.

Published: 2025-10-28 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-34317 is rated Low Risk (25/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.04%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

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

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

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

Full EPSS history (1 record total)

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

CVSS metrics for this CVE.

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]

Weakness enumeration for CVE-2025-34317

Affected software / configurations for CVE-2025-34317

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-34317

cvelogic Threat Intelligence