CVE-2026-34805
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/dnat.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 XSS vulnerability in the /cgi-bin/dnat.cgi endpoint. An authenticated attacker can inject arbitrary JavaScript through the 'remark' parameter, which persists and executes when other authenticated users view the affected page.
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 the Endian Firewall versionAccess the web management console or check the system version using the command line interface (typically via the /var/log/efw or system info pages). Locate the displayed version number.Affected if The installed version is 3.3.25 or any prior version (3.3.x series before 3.3.25).
-
Verify web interface accessibilityConfirm that the Endian Firewall web management interface (typically on port 10443 or 443) is accessible and operational.Affected if The web interface is reachable, indicating the attack surface exists.
-
Confirm DNAT functionality is accessibleLog into the web management console and navigate to the DNAT configuration section (typically under Firewall > DNAT or Network > DNAT). Determine if you have permissions to access this feature.Affected if The DNAT configuration page (dnat.cgi) is accessible to your authenticated user account.
-
Check for existing XSS in remark fieldIf you have access, view existing DNAT rule configurations and inspect the 'remark' or 'description' fields for any unexpected HTML or script content that may have been injected by another user.Affected if The remark field displays unsanitized content (script tags, event handlers, or unusual characters that render as HTML/JavaScript in the browser).
You are affected if your Endian Firewall Community version is 3.3.25 or prior AND the web interface with DNAT access is exposed to untrusted users who could inject malicious remark values.
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 on the 'remark' parameter in the dnat.cgi script. Until an official patch is available, limit access to the management interface to trusted users only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34805 — 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-34805 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