dbcve.org
Firewall CommunityApplication · Endian

CVE-2026-34810

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/vpnfw.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 3.3.25 and prior contains a stored XSS vulnerability in the /cgi-bin/vpnfw.cgi script. The 'remark' parameter lacks proper input sanitization, allowing authenticated attackers to inject malicious JavaScript that persists on the page and executes when other users view it.

MitigationImplement proper input validation and output encoding for the remark parameter. Apply context-aware escaping before rendering user-supplied data in HTML. Consider Content Security Policy headers as defense-in-depth.

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
    Check if Endian Firewall Community is installed by looking for the product in your system. On the firewall web interface, log in and check the dashboard or system information page for the product name and version.
    Affected if The installed product is Endian Firewall Community version 3.3.25 or prior.
  2. Determine installed version number
    Navigate to the Endian Firewall web interface (usually at https://your-firewall-ip:10443). Log in as an administrator and look for the version information, typically found in the System menu under Status, Dashboard, or About. Compare your version to 3.3.25.
    Affected if The installed version is 3.3.25 or any version prior to 3.3.25.
  3. Verify vpnfw.cgi is accessible
    Check if the /cgi-bin/vpnfw.cgi endpoint is accessible on your firewall. This is typically found within the VPN or Firewall settings sections of the web interface. Confirm the CGI script exists and is reachable.
    Affected if The vpnfw.cgi script exists and is accessible in the web interface.
  4. Identify remark parameter in vpnfw.cgi
    Within the VPN firewall settings (where vpnfw.cgi handles requests), locate forms or interfaces that accept a 'remark' or comment parameter. This is typically used when creating or editing VPN firewall rules.
    Affected if The vpnfw.cgi interface includes a 'remark' parameter field that accepts user input.
  5. Inspect for stored XSS in remark field
    Review any stored configuration files, database entries, or logs related to the vpnfw.cgi module. Look for any previously saved 'remark' values that may contain HTML or JavaScript characters like <script>, javascript:, onerror=, or other XSS vectors.
    Affected if The remark field contains persisted data with unsanitized HTML or script content.

You are affected if you are running Endian Firewall Community version 3.3.25 or prior and the vpnfw.cgi interface with the 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.

From vendor data
Upgrade available Upgrade to a release after 3.3.25
Interim mitigation

Implement proper input validation and output encoding for the remark parameter. Apply context-aware escaping before rendering user-supplied data in HTML. Consider Content Security Policy headers as defense-in-depth.

Fix this in Firewall Community Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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