Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-9585

HIGH · 8.6 CVSS v4.0 Published 2026-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable No privileges 5 weeks old

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 · unedited
An unauthenticated reflected cross-site scripting (XSS) vulnerability exists in Sangoma Switchvox SMB Edition version 8.3 (104997). The application fails to properly sanitize the portal parameter supplied to the invalid_browser and invalid_browser_login handlers. User-supplied data is reflected into JavaScript generated by the application, allowing attacker-controlled script execution within a victim's browser.

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 confidence

An unauthenticated reflected XSS vulnerability exists in Sangoma Switchvox SMB Edition v8.3 (104997). The portal parameter in the invalid_browser and invalid_browser_login handlers fails to sanitize user input, which gets reflected directly into JavaScript context, allowing arbitrary script execution.

MitigationImplement proper input validation and output encoding for the portal parameter in the vulnerable handlers to prevent script injection.

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
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Sangoma Switchvox SMB Edition installation
    Identify if the target system is running Sangoma Switchvox SMB Edition. Check the web interface for Switchvox branding, or inspect running processes/services on the system for switchvox-related processes. The application typically runs on standard web ports (443, 8443).
    Affected if The system is running Sangoma Switchvox SMB Edition
  2. Verify the installed version
    Locate the version information by checking the Switchvox admin interface login page for version/build numbers, or inspecting system files such as /opt/switchvox/etc/version or similar configuration files. Confirm the exact version is 8.3 with build 104997.
    Affected if Version is exactly 8.3 (build 104997)
  3. Determine if the web interface is accessible
    Test connectivity to the Switchvox web interface ports. Since this is an unauthenticated reflected XSS, the vulnerable handlers must be reachable without authentication. Confirm the web application is network-accessible.
    Affected if Web interface is accessible without authentication
  4. Inspect the vulnerable parameter handlers
    Review web server logs or application logs for requests to the invalid_browser or invalid_browser_login endpoints. Check if the application processes the 'portal' parameter and reflects it into the response without sanitization by examining the application's request handling code or proxy configuration.
    Affected if The application processes the portal parameter in invalid_browser or invalid_browser_login handlers without output encoding

A system is affected if it runs Sangoma Switchvox SMB Edition version 8.3 build 104997 with an accessible web interface where the portal parameter in invalid_browser or invalid_browser_login handlers reflects user input without sanitization into JavaScript context.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for the portal parameter in the vulnerable handlers to prevent script injection.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9585 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9585 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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