CVE-2026-34802
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 user ham spam parameter to /cgi-bin/salearn.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 versions 3.3.25 and prior contain a stored cross-site scripting (XSS) vulnerability in the /cgi-bin/salearn.cgi script. An authenticated attacker can inject arbitrary JavaScript through the remark user ham spam parameter, which persists and executes when other 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 Endian Firewall installation and versionAccess the admin interface or check system version using: cat /etc/efw_version or grep -i version /etc/*release 2>/dev/nullAffected if Version is 3.3.25 or lower (Community edition)
-
Confirm the salearn.cgi script existsVerify the CGI script exists at /cgi-bin/salearn.cgi on the web server rootAffected if The salearn.cgi script is present in the CGI directory
-
Verify administrative or user authentication is enabledCheck if user accounts exist and the web interface is accessible for authenticated usersAffected if Users can authenticate to the Endian Firewall web interface
-
Identify access to the spam learning featureNavigate to the spam learning/filtering section in the web UI where the 'remark user ham spam' parameter is used, or inspect the salearn.cgi parametersAffected if The spam learning functionality with the remark parameter is accessible to authenticated users
-
Check for existing malicious script injectionsReview web server logs or database entries for unusual script tags in the remark user ham spam parameter, or view the salearn.cgi page source as another userAffected if Persistent JavaScript or HTML tags appear in the remark field that are not properly escaped
A user is affected if running Endian Firewall Community version 3.3.25 or lower with the salearn.cgi spam learning feature accessible to authenticated users, and the 'remark user ham spam' parameter contains unsanitized input that could execute JavaScript.
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 dataApply available vendor patches or updates to Endian Firewall. If no patch exists, implement input validation and output encoding on the remark parameter in salearn.cgi to neutralize malicious script content.
- Consultation3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34802 — 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-34802 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