dbcve.org
Firewall CommunityApplication · Endian

CVE-2026-34814

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-02
Fix available
A fix is available. Upgrade to after 3.3.25 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 stored cross-site scripting (XSS) via the group parameter to /cgi-bin/proxygroup.cgi. An authenticated attacker can inject arbitrary JavaScript that is stored and executed when other users view the affected page.

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 · moderate confidence

Endian Firewall versions 3.3.25 and prior contain a stored XSS vulnerability in the web interface. The vulnerability exists in the /cgi-bin/proxygroup.cgi script via the group parameter. An authenticated attacker can inject malicious JavaScript that persists on the page and executes in the browsers of other users who view the affected interface.

MitigationUpgrade to a patched version of Endian Firewall beyond 3.3.25; if no upgrade is available, implement input validation and output encoding on the group parameter in proxygroup.cgi, or deploy WAF rules to block XSS payloads in this endpoint.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Identify Endian Firewall version
    Access the administration interface and navigate to System > Status or check /etc/redhat-release (for RPM-based) or the web UI footer which typically displays the version number
    Affected if The displayed version is 3.3.25 or any prior version (e.g., 3.3.24, 3.3.23, etc.)
  2. Confirm proxygroup.cgi endpoint exists
    Check if the file /cgi-bin/proxygroup.cgi exists on the Endian Firewall web server by attempting to access it via browser or command line (e.g., curl http://<your-firewall-ip>/cgi-bin/proxygroup.cgi)
    Affected if The endpoint responds (returns HTTP 200 or redirects to login) rather than returning a 404 Not Found error
  3. Verify proxygroup.cgi is accessible to authenticated users
    Log into the Endian Firewall administration interface with a standard administrator account and navigate to the proxy or group configuration section where proxygroup.cgi would be invoked, or attempt a request to the endpoint with valid session credentials
    Affected if The endpoint accepts requests from authenticated administrators (the vulnerability requires an authenticated attacker, so if only completely unauthenticated access is possible, the exploitability may differ)

Your environment is affected if you are running Endian Firewall Community version 3.3.25 or earlier AND the /cgi-bin/proxygroup.cgi endpoint is accessible to authenticated administrator accounts, since the stored XSS in the group parameter will execute for other users viewing the interface.

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

Upgrade to a patched version of Endian Firewall beyond 3.3.25; if no upgrade is available, implement input validation and output encoding on the group parameter in proxygroup.cgi, or deploy WAF rules to block XSS payloads in this endpoint.

Recommended fix Moderate confidence

Endian Firewall Community 3.3.26 or later (verify actual fixed release at help.endian.com)

  1. 1. Verify the current installed version of Endian Firewall Community by accessing the web interface or checking system information
  2. 2. Check Endian's official release notes and security advisories at help.endian.com for version 3.3.26 or later
  3. 3. If a newer fixed version is available, review the release notes for migration instructions
  4. 4. Back up the current firewall configuration before upgrading
  5. 5. Follow Endian's standard upgrade procedure for the Community edition
  6. 6. After upgrade, verify the /cgi-bin/proxygroup.cgi page no longer accepts unsanitized input in the group parameter
  7. 7. If no upgrade is available, contact Endian support for patch availability
Caveat Review release notes for any breaking changes between 3.3.25 and the target version; firewall rule and configuration adjustments may be needed

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

Fix this in Firewall Community Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34814 — 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-34814 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