CVE-2026-34816
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 domain parameter to /manage/smtpscan/domainrouting/. 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 domain parameter of the /manage/smtpscan/domainrouting/ endpoint. An authenticated attacker can inject malicious JavaScript that persists in the domain field and executes when other authenticated users view the SMTPScan domain routing 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.
-
Determine Endian Firewall versionAccess the web administration interface and navigate to the System > Status or System > Information page to view the installed version number. Alternatively, check the /etc/redhat-release file or the package management system for the endian-firewall version.Affected if The installed version is 3.3.25 or lower
-
Verify SMTPScan module is accessibleLog into the Endian Firewall web interface and attempt to navigate to the SMTPScan domain routing page at /manage/smtpscan/domainrouting/ or locate it within the Mail section of the administration panel.Affected if The SMTPScan domain routing functionality exists and is accessible in the interface
-
Inspect domain routing configuration for suspicious entriesAccess the SMTPScan domain routing configuration page and review all configured domains. Look for any domain entries containing HTML tags, JavaScript code, or unusual characters such as <script>, javascript:, onload, or other XSS payloads.Affected if Any domain entry contains unsanitized HTML or JavaScript code that could execute in a browser
-
Check database or configuration files for malicious domain entriesExamine the backend database or configuration files that store the SMTPScan domain routing settings. Look for the domain parameter values and inspect them for encoded or obfuscated XSS payloads.Affected if Stored domain values contain malicious script content that would execute when displayed in the web interface
A user is affected if they are running Endian Firewall Community version 3.3.25 or lower AND have access to the SMTPScan domain routing feature, with any domain entries containing unsanitized JavaScript or HTML content present in the configuration.
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 strict input validation on the domain parameter combined with proper output encoding when displaying the domain value to prevent script execution. Consider implementing Content Security Policy headers as a defense-in-depth measure.
- 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-34816 — 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-34816 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