dbcve.org
Firewall CommunityApplication · Endian

CVE-2026-34799

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 /manage/dnsmasq/hosts/. 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 DNSmasq hosts management interface. The 'remark' parameter at /manage/dnsmasq/hosts/ does not properly sanitize user input, allowing an authenticated attacker to inject arbitrary JavaScript that persists on the page and executes in the browsers of other users who view the affected resource.

MitigationImplement strict input validation and contextual output encoding for the remark parameter to prevent script injection. The fix should sanitize or reject special characters before storage and properly encode all user-supplied content when rendered in HTML.

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 Community version
    Access the system administration interface or use the command line to retrieve the installed Endian Firewall version. Typically found in the dashboard or via system info page.
    Affected if Version displayed is 3.3.25 or any lower version number.
  2. Confirm version falls within affected range
    Compare your installed version against the known affected range: Community version 3.3.25 and prior.
    Affected if The installed version is 3.3.25 or lower.
  3. Verify DNS hosts management interface is accessible
    Log into the Endian Firewall admin interface and navigate to the DNS hosts management section, typically found under Services or Network settings. Access the path /manage/dnsmasq/hosts/ if directly reachable.
    Affected if The DNS hosts management interface is accessible and the 'remark' parameter field is present for DNS host entries.
  4. Check for existing malicious entries in DNS hosts
    Review the DNS hosts table/list for any unexpected or suspicious entries in the remark/comment fields that may contain script tags or encoded JavaScript.
    Affected if Any DNS host entries contain unsanitized HTML or JavaScript in the remark field.

A system is affected if it runs Endian Firewall Community version 3.3.25 or lower and has the DNS hosts management interface accessible with the vulnerable 'remark' parameter.

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 contextual output encoding for the remark parameter to prevent script injection. The fix should sanitize or reject special characters before storage and properly encode all user-supplied content when rendered in HTML.

Recommended fix Moderate confidence

Endian Firewall Community version > 3.3.25 (latest stable release)

  1. 1. Identify the current Endian Firewall Community version installed using the web UI or command line (grep version /etc/*release or check the dashboard)
  2. 2. Navigate to the Endian Firewall download portal or support page at help.endian.com
  3. 3. Download the latest stable release of Endian Firewall Community (version higher than 3.3.25)
  4. 4. Create a backup of the current configuration via the web UI (System > Backup > Download configuration)
  5. 5. Review the upgrade documentation specific to your current version
  6. 6. Perform the upgrade following the official upgrade procedure, ensuring power stability during the process
  7. 7. After upgrade, verify the /manage/dnsmasq/hosts/ page now sanitizes the remark parameter properly
  8. 8. Confirm no XSS payloads previously injected remain in the hosts configuration and clean if necessary
Caveat Minor: Review release notes for any configuration format changes between 3.3.25 and the target version; test in staging before production deployment

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
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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