dbcve.org
Firewall CommunityApplication · Endian

CVE-2026-34817

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 ADDRESS BCC parameter to /cgi-bin/smtprouting.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 · high confidence

Endian Firewall 3.3.25 and prior contains a stored XSS vulnerability in the smtprouting.cgi interface. The ADDRESS BCC parameter accepts unsanitized input that is stored and reflected back without proper output encoding, allowing injection of arbitrary JavaScript that executes in the browsers of other authenticated users who view the affected page.

MitigationImplement strict input validation and sanitization on the ADDRESS BCC parameter, combined with proper output encoding when displaying the data. Consider adding a Content Security Policy header to further mitigate XSS risks.

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 installation and version
    Check the installed Endian Firewall Community version by accessing the web interface login page or running 'rpm -q endian-firewall' or 'cat /etc/redhat-release' if installed via RPM. Compare against the affected version 3.3.25 and prior.
    Affected if The installed version is 3.3.25 or any version prior to 3.3.25
  2. Verify the web interface is enabled
    Confirm the Endian Firewall web GUI (HTTP/HTTPS on ports 80/443 or 10443) is accessible and running. Check with 'systemctl status httpd' or 'systemctl status nginx' depending on the web server in use.
    Affected if The web interface is exposed and accessible to the attacker
  3. Confirm smtprouting.cgi exists and is accessible
    Attempt to access the path /cgi-bin/smtprouting.cgi via the web interface using a browser or curl command (e.g., curl -k https://<your-firewall-ip>/cgi-bin/smtprouting.cgi). Verify the page loads or returns a valid HTTP response.
    Affected if The smtprouting.cgi script exists and is accessible without authentication restrictions or the attacker has valid credentials
  4. Check if SMTP routing with ADDRESS BCC is configurable
    Log into the web interface as an authenticated user and navigate to the SMTP routing settings. Look for a field labeled 'ADDRESS BCC' or similar BCC routing configuration options.
    Affected if The ADDRESS BCC parameter field exists and accepts user input without sanitization; the injected payload would persist and execute when other users view the page

A user is affected if Endian Firewall Community version 3.3.25 or prior is installed, the web interface is accessible, and the smtprouting.cgi script with the ADDRESS BCC parameter is available and accepts unsanitized input.

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

Implement strict input validation and sanitization on the ADDRESS BCC parameter, combined with proper output encoding when displaying the data. Consider adding a Content Security Policy header to further mitigate XSS risks.

Recommended fix Moderate confidence

Latest Endian Firewall Community release (version > 3.3.25)

  1. 1. Backup current Endian Firewall configuration before making any changes
  2. 2. Download the latest Endian Firewall Community release from the official vendor repository
  3. 3. Verify the integrity of the downloaded image using checksums if provided
  4. 4. Plan a maintenance window as the upgrade may require downtime
  5. 5. Perform the upgrade following Endian's official upgrade documentation
  6. 6. After upgrade, verify the /cgi-bin/smtprouting.cgi interface is accessible and functional
  7. 7. Test that the ADDRESS BCC parameter now properly sanitizes input
Caveat Review Endian release notes for breaking changes between 3.3.25 and the target version; Community edition may have limited features compared to Enterprise

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

Fix this in Firewall Community Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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