CVE-2026-34818
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 /manage/dnsmasq/localdomains/. 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 /manage/dnsmasq/localdomains/ endpoint. The 'remark' parameter accepts unsanitized user input, allowing an authenticated attacker to inject malicious JavaScript that persists on the page and executes in the browsers of other users who 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 installationConfirm the target system is running Endian Firewall. This is typically a dedicated network appliance or Linux-based system with the Endian web interface accessible on port 443 or 10443.Affected if The system is running Endian Firewall Community edition web interface.
-
Check installed versionLog into the Endian Firewall web UI and navigate to the System > Status page, or run the command 'cat /etc/e-smith-release' via SSH to retrieve the exact version number. Compare against 3.3.25.Affected if The installed version is 3.3.25 or any version prior to 3.3.25.
-
Verify dnsmasq module is enabledAccess the web UI and navigate to the DNSmasq section under Services, or inspect the configuration file /var/tmp/e-smith/db/dnsmasq/ configuration to confirm the DNSmasq service is active.Affected if The DNSmasq service is enabled and the local domains management interface is accessible.
-
Confirm vulnerable endpoint is accessibleAttempt to access the URL path /manage/dnsmasq/localdomains/ via the web browser while authenticated. If the page loads with a form containing a 'remark' or comment field, the endpoint is present.Affected if The /manage/dnsmasq/localdomains/ endpoint is accessible and displays a form with an input field for remarks or comments.
A system is affected if it runs Endian Firewall Community version 3.3.25 or lower, has the DNSmasq service enabled, and exposes the web management interface with access to the local domains configuration page.
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 output encoding and input validation/sanitization on the remark parameter to neutralize HTML/JavaScript payloads before storage and display. If a patched version is available, upgrade to a version beyond 3.3.25.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34818 — 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-34818 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