Skip to content

CVE-2025-34311

OS Command Injection: Is CVE-2025-34311 real, exploitable, or a false positive? Here's the community verdict.

signals

public sources

Exploited in wild
Not listed
CISA KEV
Public exploit
None known
Metasploit/EDB/PoC
Base severity
8.8 High
CVSS
Exploitation prob.
14%
FIRST EPSS
Weakness
CWE-78 · OS Command Injection
CWE

Moderate signals. Triage by your actual exposure and reachability.

cisa ssvc

CISA Vulnrichment · assessed

Exploitation
None
in the wild
Automatable
No
at scale
Technical impact
Total
on success

CISA decision, by how critical the affected system is to you:

  • low impact → Track
  • medium impact → Track
  • high impact → Track*

Track: normal patch cycle · Track*: watch closely · Attend: patch sooner · Act: patch now. About SSVC ↗

baseline read

auto · not a community verdict

Low signal — verdict needed

Few public signals point to active risk. Whether a scanner hit here is a true or false positive depends on your version and config — community verdicts decide.

Based on CVSS · FIRST EPSS

Confirm or dispute →

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 user 'nobody' via multiple parameters when creating a Proxy report. When a user creates a Proxy report the application issues an HTTP POST to /cgi-bin/logs.cgi/calamaris.dat and reads the values of DAY_BEGIN, MONTH_BEGIN, YEAR_BEGIN, DAY_END, MONTH_END, YEAR_END, NUM_DOMAINS, PERF_INTERVAL, NUM_CONTENT, HIST_LEVEL, NUM_HOSTS, NUM_URLS, and BYTE_UNIT, which are interpolated directly into the shell invocation of the mkreport helper. Because these parameters are never sanitized for improper characters or constructs, a crafted POST can inject shell metacharacters into one or more fields, causing arbitrary commands to run with the privileges of the 'nobody' user.

Published

Embed this verdict
TruePositive verdict for CVE-2025-34311
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2025-34311/badge.svg)](https://www.truepositive.app/cve/CVE-2025-34311)
HTML
<a href="https://www.truepositive.app/cve/CVE-2025-34311"><img src="https://www.truepositive.app/cve/CVE-2025-34311/badge.svg" alt="TruePositive verdict for CVE-2025-34311"></a>

Live badge that updates automatically as the community verdict changes.

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: A curated baseline from public sources, shown separately from community verdicts.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    No confirmed in-the-wild exploitation or public exploit was found for this yet. FIRST EPSS estimates about a 14% chance of exploitation in the next 30 days, which is high relative to most CVEs.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.

Same weakness: CWE-78 · OS Command Injection.