CVE-2026-30695
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 · uneditedA Cross-Site Scripting (XSS) vulnerability exists in the web-based configuration interface of Zucchetti Axess access control devices, including XA4, X3/X3BIO, X4, X7, and XIO / i-door / i-door+. The vulnerability is caused by improper sanitization of user-supplied input in the dirBrowse parameter of the /file_manager.cgi endpoint.
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 · moderate confidenceA stored XSS vulnerability exists in the web-based configuration interface of Zucchetti Axess access control devices (XA4, X3/X3BIO, X4, X7, XIO/i-door/i-door+). The dirBrowse parameter in /file_manager.cgi fails to sanitize user-supplied input, allowing injection of malicious JavaScript that executes in the context of other users' sessions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 the Zucchetti Axess device modelCheck the device label, management interface header, or system information page for the model number. Affected models include XA4, X3/X3BIO, X4, X7, and XIO/i-door/i-door+.Affected if The device is one of these specific models.
-
Confirm web-based management interface is enabledAccess the device IP address via HTTP/HTTPS in a web browser. Look for the Zucchetti Axess login page or configuration interface.Affected if The web interface is accessible and shows a Zucchetti Axess login or configuration page.
-
Verify /file_manager.cgi endpoint existsNavigate to http[s]://[device-ip]/file_manager.cgi or check if this endpoint responds (may require authentication first).Affected if The /file_manager.cgi endpoint exists and is accessible on the device.
-
Check for dirBrowse parameter usageExamine the HTTP requests when using the file manager interface, or inspect the page source for the dirBrowse parameter in forms or URLs.Affected if The dirBrowse parameter is present in requests or page source within the file manager functionality.
-
Assess input sanitization on dirBrowseSubmit a test value containing characters like <script>alert(1)</script> or '" onclick= in the dirBrowse parameter and observe if the value is reflected back unescaped in the response.Affected if User-supplied input in the dirBrowse parameter is reflected in the response without proper HTML encoding or sanitization.
If the device is one of the affected Zucchetti Axess models (XA4, X3/X3BIO, X4, X7, XIO/i-door/i-door+) and the web interface with /file_manager.cgi is accessible, the environment is potentially affected by this stored XSS vulnerability.
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 output encoding on the dirBrowse parameter in /file_manager.cgi; applyContextual escaping for all user-controlled data rendered in HTML. If available, apply vendor firmware updates.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30695 — 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-30695 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