CVE-2026-34822
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 new_cert_name parameter to /manage/ca/certificate/. 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 certificate management interface. The vulnerability exists in the /manage/ca/certificate/ endpoint where the new_cert_name parameter is not properly sanitized, allowing an authenticated attacker to embed malicious JavaScript that persists on the page and executes when other users view the affected certificate management 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.
-
Confirm Endian Firewall Community is installedIdentify if the Endian Firewall Community product is present in your environment. This may be visible in system information, running services, or installed packages.Affected if Endian Firewall Community is not installed - you are not affected.
-
Check installed version numberDetermine the exact version of Endian Firewall Community installed in your environment. Compare it against the affected range: version 3.3.25 and prior.Affected if The installed version is 3.3.25 or lower - you are within the affected version range.
-
Verify certificate management module is accessibleConfirm that the certificate management functionality at /manage/ca/certificate/ is accessible to authenticated users in your environment. Check if this endpoint responds to requests.Affected if The /manage/ca/certificate/ endpoint exists and is accessible to authenticated users - the attack surface is present.
-
Inspect input handling for new_cert_name parameterExamine how the new_cert_name parameter in the certificate management interface handles user input. Look for whether the parameter accepts and stores data without sanitization.Affected if The new_cert_name parameter accepts and stores input without proper validation or encoding - the vulnerability is present.
You are affected if Endian Firewall Community version 3.3.25 or prior is installed, the /manage/ca/certificate/ endpoint is accessible to authenticated users, and the new_cert_name parameter does not sanitize or encode input before storage.
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 new_cert_name parameter and all user-supplied data in the certificate management module. Use context-appropriate encoding when displaying certificate names and employ a content security policy to provide defense-in-depth against XSS attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34822 — 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-34822 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