dbcve.org
Firewall CommunityApplication · Endian

CVE-2026-34811

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 remark parameter to /cgi-bin/xtaccess.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 versions 3.3.25 and prior contain a stored cross-site scripting vulnerability in the /cgi-bin/xtaccess.cgi endpoint. The 'remark' parameter accepts unsanitized user input, allowing an authenticated attacker to inject malicious JavaScript that persists on the server and executes in the browsers of other users who access the affected page.

MitigationImplement robust input validation and output encoding on the 'remark' parameter at the /cgi-bin/xtaccess.cgi endpoint to neutralize script injection attempts. Consider deploying a web application firewall rule as an interim control.

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 admin interface or check system package version via command line (e.g., 'rpm -q endian-firewall' or check /etc/redhat-release for Endian version)
    Affected if Installed version is 3.3.25 or lower
  2. Verify xtaccess.cgi endpoint exists
    Check if /cgi-bin/xtaccess.cgi is present on the system - typically found in /var/www/cgi-bin/ or equivalent web root directory
    Affected if The CGI script file exists on the system
  3. Check authentication access to the affected endpoint
    Attempt to access /cgi-bin/xtaccess.cgi with valid admin credentials to confirm the endpoint is accessible
    Affected if User can authenticate and access the xtaccess.cgi interface
  4. Inspect remark parameter storage
    Examine the configuration or database where the 'remark' parameter is stored - typically in access control or firewall rule configurations
    Affected if The 'remark' field accepts and stores user-supplied text without sanitization
  5. Look for injected script content in stored data
    Review saved configurations or exported rule sets for any HTML tags, script elements, or JavaScript event handlers in remark/description fields
    Affected if Unsanitized script tags or JavaScript code is found stored in any remark field

A user is affected if they are running Endian Firewall Community version 3.3.25 or lower and the xtaccess.cgi endpoint with its 'remark' parameter is accessible to authenticated users.

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 robust input validation and output encoding on the 'remark' parameter at the /cgi-bin/xtaccess.cgi endpoint to neutralize script injection attempts. Consider deploying a web application firewall rule as an interim control.

Recommended fix Moderate confidence

Endian Firewall Community version > 3.3.25 (latest available stable release)

  1. 1. Back up the current Endian Firewall configuration before making any changes.
  2. 2. Obtain the latest version of Endian Firewall Community (version > 3.3.25) from the official vendor repository at endian.com or through the official update mechanism.
  3. 3. Apply the upgrade following the vendor's documented upgrade procedure for the Community edition.
  4. 4. After upgrade, verify the /cgi-bin/xtaccess.cgi page loads correctly and the remark parameter is properly sanitized.
  5. 5. Log in as an administrator and confirm the web interface functions normally after the upgrade.
Caveat Review Endian release notes for the target version to check for configuration changes or migration requirements that may affect firewall rules or network settings.

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-34811 — 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-34811 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