CVE-2025-34312 | IPFire < v2.29 Command Injection via URL Filter Blacklist

IPFire versions prior to 2.29 (Core Update 198) contain a command injection vulnerability that allows an authenticated attacker to execute arbitrary commands as the 'nobody' user via the BE_NAME parameter when installing a blacklist. When a blacklist is installed the application issues an HTTP POST to /cgi-bin/urlfilter.cgi and interpolates the value of BE_NAME directly into a shell invocation without appropriate sanitation. Crafted input can inject shell metacharacters, leading to arbitrary command execution in the context of the 'nobody' user.

Published: 2025-10-28 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-34312 is rated Moderate Risk (63.4/100): CVSS High severity, with medium exploitation likelihood (EPSS 2.30%). Mandatory action: Review affected assets and schedule remediation.

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

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 2026-06-25 2.05% 2.30% +0.24%
2 2026-06-15 0.36% 2.05% +1.70%
3 2026-05-24 0.36%

Full EPSS history (12 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.7 4.0 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/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:N)
No user interaction is required.
Vulnerable system confidentiality impact (VC:H)
High confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:H)
High integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:H)
High availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:N)
No confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:N)
No 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]
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H 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:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.8 5.9 [email protected]

Weakness enumeration for CVE-2025-34312

Affected software / configurations for CVE-2025-34312

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

cvelogic Threat Intelligence