CVE-2026-34806
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 · uneditedEndian Firewall version 3.3.25 and prior allow stored cross-site scripting (XSS) via the remark parameter to /cgi-bin/snat.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 confidenceEndian Firewall 3.3.25 and prior contains a stored cross-site scripting (XSS) vulnerability in the /cgi-bin/snat.cgi endpoint. The 'remark' parameter does not properly sanitize user input, allowing an authenticated attacker to inject malicious JavaScript that persists on the page and executes when other users view the affected interface.
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<= 3.3.25CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Endian Firewall versionCheck the installed Endian Firewall version by examining system files or the web interface login page. Look for version information in /etc/ endian-release or similar version files, or view the version displayed in the web UI footer.Affected if Installed version is 3.3.25 or any version prior to 3.3.25
-
Confirm web interface is accessibleVerify the Endian Firewall web interface CGI binaries are accessible by attempting to reach /cgi-bin/snat.cgi or the main login page. Check HTTP service status.Affected if The web interface responds and CGI scripts are executable
-
Check authentication configurationReview the web interface authentication settings to determine if user logins are enabled. Examine whether the remark parameter can be accessed by authenticated users.Affected if Web interface authentication is enabled and users can access the SNAT configuration page with their credentials
-
Inspect SNAT configuration for suspicious remarksExamine the SNAT configuration data for the remark field in /var/efw/snat/rules or equivalent configuration storage. Search for any HTML or JavaScript code patterns in remark values.Affected if Any remark value contains unescaped HTML tags, script elements, or JavaScript event handlers such as onload, onerror, or onclick
A user is affected if they are running Endian Firewall Community version 3.3.25 or prior, have the web interface enabled with authenticated access, and the SNAT remark parameter contains injected script content.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper input validation and output encoding for the remark parameter in snat.cgi. Additionally, apply context-aware output escaping when the remark field is rendered to prevent XSS execution.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34806 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34806 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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