CVE-2026-34823
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/password/web/. 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 confidenceA stored cross-site scripting (XSS) vulnerability in Endian Firewall version 3.3.25 and prior allows authenticated attackers to inject arbitrary JavaScript via the 'remark' parameter at the /manage/password/web/ endpoint. The malicious payload is stored persistently and executes in the browsers of other users when they 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 installed Endian Firewall versionAccess the web management interface and navigate to the System Status or Settings page to view the version information. Alternatively, check the /etc/redhat-release file or run 'cat /etc/issue' via console if you have CLI access.Affected if The displayed version number is 3.3.25 or lower.
-
Verify web management interface is enabledConfirm that the web-based management interface (HTTP/HTTPS on port 10443 or 443) is active and accessible. Check if the service is running via 'systemctl status httpd' or 'systemctl status apache2' depending on the underlying system.Affected if The web interface is exposed and accessible to authenticated users.
-
Confirm access to the vulnerable endpointLog into the Endian Firewall web management interface and navigate to the /manage-password/web/ URL path. Verify the page loads and contains input fields.Affected if The /manage-password/web/ endpoint is accessible and displays a form with input parameters.
-
Check for existing malicious payloads in the remark fieldIf you have database access, query the application database (typically MySQL or PostgreSQL) for stored XSS payloads in tables related to password management or user configurations. Look for HTML script tags or JavaScript code in the remark field.Affected if Script tags or encoded JavaScript characters are found stored in the remark parameter database field.
Your environment is affected if you are running Endian Firewall Community version 3.3.25 or lower and the web management interface is accessible, as the stored XSS vulnerability in the remark parameter at /manage-password/web/ can be exploited by authenticated attackers.
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 and context-aware output encoding for the 'remark' parameter, and consider adding Content Security Policy (CSP) headers to provide defense-in-depth against XSS attacks.
- 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-34823 — 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-34823 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