dbcve.org
Firewall CommunityApplication · Endian

CVE-2026-34791

HIGH · 8.8 CVSS v3.1 Published 2026-04-02
Fix available
A fix is available. Upgrade to after 3.3.25 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Endian Firewall version 3.3.25 and prior allow authenticated users to execute arbitrary OS commands via the DATE parameter to /cgi-bin/logs_proxy.cgi. The DATE parameter value is used to construct a file path that is passed to a Perl open() call, which allows command injection due to an incomplete regular expression validation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Endian Firewall versions 3.3.25 and prior contain an authenticated command injection vulnerability in /cgi-bin/logs_proxy.cgi. The DATE parameter is used to construct a file path passed to a Perl open() call without proper sanitization, allowing authenticated users to inject arbitrary OS commands through incomplete regular expression validation.

MitigationApply vendor patch when available, or implement strict input validation with whitelist filtering on the DATE parameter before use in file path construction. Consider refactoring to avoid Perl open() with user-controlled input.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Firewall CommunityApplication
Affected:<= 3.3.25

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Endian Firewall installation
    Identify the installed product by checking system information or looking for Endian Firewall-specific files, such as /var/log/efw or checking the web interface banner for 'Endian' branding.
    Affected if The system is running Endian Firewall Community edition.
  2. Check installed version
    Determine the installed version of Endian Firewall. This may be available in the web interface status page, or via command line looking for version files such as /etc/redhat-release (if applicable) or /var/www/html/api/status. Typical locations include /etc/ endian-version or the admin web interface dashboard.
    Affected if The installed version is 3.3.25 or any prior version (e.g., 3.3.24, 3.3.20, etc.).
  3. Verify logs_proxy.cgi exists
    Check for the presence of the affected CGI script at /cgi-bin/logs_proxy.cgi on the web server. This can be done via file system inspection or by attempting to access the URL (requires authentication).
    Affected if The file /cgi-bin/logs_proxy.cgi exists on the system.
  4. Confirm web interface authentication is enabled
    Verify that the Endian Firewall web management interface is accessible and that user authentication is configured. The vulnerability requires an authenticated session to exploit.
    Affected if The web interface is accessible and authentication is enabled or configurable.
  5. Inspect DATE parameter handling in logs_proxy.cgi
    If direct code inspection is possible, examine the logs_proxy.cgi script to verify it uses the DATE parameter in a Perl open() call without proper sanitization. Look for patterns like 'open()' or 'sysopen()' using the DATE parameter in file path construction.
    Affected if The CGI script uses the DATE parameter in an open() call without validated sanitization.

A system is affected if it runs Endian Firewall Community version 3.3.25 or prior, has the logs_proxy.cgi script present, and has the web management interface with authentication enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.3.25
Interim mitigation

Apply vendor patch when available, or implement strict input validation with whitelist filtering on the DATE parameter before use in file path construction. Consider refactoring to avoid Perl open() with user-controlled input.

Recommended fix Moderate confidence

Latest Endian Firewall Community version (verify version > 3.3.25 at help.endian.com)

  1. 1. Identify the current Endian Firewall Community version by navigating to the web interface or checking system information.
  2. 2. Back up all configuration files and firewall rules before performing any upgrade.
  3. 3. Download the latest Endian Firewall Community release from the official vendor repository (help.endian.com) or official download channels.
  4. 4. Review the release notes for the new version to confirm the command injection vulnerability (CVE-2026-34791) is addressed.
  5. 5. Schedule a maintenance window as the upgrade may require system restart.
  6. 6. Execute the upgrade following the vendor's documented upgrade procedure for Endian Firewall Community.
  7. 7. After upgrade, verify the system is operational and test that /cgi-bin/logs_proxy.cgi functions correctly with valid input.
  8. 8. Confirm the DATE parameter now properly validates input and rejects command injection attempts.
Caveat Review release notes for potential breaking changes between 3.3.25 and newer versions; Community edition may have limited features compared to commercial editions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firewall Community Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34791 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34791 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data