CVE-2026-34808
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/outgoingfw.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 confidenceStored cross-site scripting (XSS) vulnerability in Endian Firewall versions 3.3.25 and prior. The 'remark' parameter in /cgi-bin/outgoingfw.cgi does not properly sanitize user input, allowing an authenticated attacker to inject malicious JavaScript that is stored on the server and executed in the browsers of other users who 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 Endian Firewall installationLocate the Endian Firewall installation directory or check system packages for endian-firewall or efw packagesAffected if Endian Firewall Community is not installed on the system
-
Determine installed versionRun package manager query or check version file for endian-firewall version (for example: rpm -q endian-firewall, dpkg -l endian-firewall, or cat /var/log/Endian/version)Affected if The installed version is 3.3.25 or any version prior to 3.3.25
-
Verify outgoingfw.cgi script existsCheck for the presence of /cgi-bin/outgoingfw.cgi in the web root directory (typically /var/www/html/cgi-bin/ or /usr/shareEndian/var/www/cgi-bin/)Affected if The outgoingfw.cgi script exists in the expected CGI directory
-
Confirm remark parameter handlingInspect the outgoingfw.cgi source code or configuration to verify the 'remark' parameter is processed and stored without proper input validationAffected if The script accepts and stores the 'remark' parameter without sanitization
-
Check authentication requirementReview the CGI script and web server configuration to confirm outgoingfw.cgi requires authentication for accessAffected if The script is accessible to authenticated users and stores data that other users can view
-
Verify stored data is rendered unsafelyExamine how stored remarks are displayed in the web interface - look for lack of output encoding when the remark is rendered in HTML contextAffected if Stored remarks are displayed without proper output encoding, allowing script injection
A user is affected if they have Endian Firewall Community version 3.3.25 or prior installed with the outgoingfw.cgi script accessible to authenticated users who can store remarks that are rendered without encoding.
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. Upgrade to a version newer than 3.3.25 if available, or apply vendor-provided patches.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34808 — 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-34808 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