CVE-2026-9586 — Sangoma Switchvox: SQL Injection | CVSS 9.3 CRITICAL

CRITICAL

CVSS 9.3 CRITICAL  ·  EPSS 1%  ·  Sangoma Switchvox

Severity Overview

Summary

An unauthenticated SQL injection vulnerability exists in Sangoma Switchvox SMB Edition 8.3 (104997). The /pa endpoint processes XML content beginning with <PolycomIPPhone> and directly concatenates the user-controlled PhoneIP value into PostgreSQL queries without sanitization or parameterization. An unauthenticated remote attacker can execute arbitrary SQL statements against the backend PostgreSQL database using a single crafted request, including database operations and remote code execution.

What the Attack Looks Like

How it works: Attacker-controlled input is inserted into a SQL query without sanitization. The database executes the modified query, which can expose data, bypass authentication, or in some configurations execute commands on the host.

If successfully exploited: The lateral movement potential mapped to T1210 means an attacker who gains initial access through this CVE may be able to spread to adjacent systems before detection.

Analyst Takeaway

The attack is launched over the network (remotely exploitable without physical access) and no authentication is required. This vulnerability is already in CISA KEV, which means exploitation has been confirmed in the wild — treat this as active risk, not theoretical exposure. The CVSS score places this in critical territory, so internet-facing systems and high-value assets should be prioritized for immediate remediation or compensating controls. Because the mapping suggests remote service exploitation potential, defenders should also consider post-compromise lateral movement scenarios during investigation. In parallel with patching, defenders should review external exposure, hunt for signs of exploitation, and validate whether compensating controls are in place for vulnerable assets.

MITRE ATT&CK Mapping

• T1210 – Exploitation of Remote Services
  Rationale: The vulnerability context suggests exploitation of services commonly used for remote access or lateral movement.

Detection Guidance

• CWE-89 — SQL Injection
  • WAF and application logs: Search request parameters for SQL syntax: UNION SELECT, OR 1=1, -- (comment sequences), single quotes, SLEEP(, WAITFOR DELAY, BENCHMARK(, and their URL-encoded forms. Time-based blind injection may not appear in app logs but will show anomalous response latency.
  • Database error logs: A spike in query syntax errors from the application’s database user is a strong injection indicator. Legitimate traffic rarely generates SQL errors in bulk.
  • Database activity monitoring: Look for queries accessing tables outside the application’s normal working set, unexpected SELECT * across sensitive tables, or INFORMATION_SCHEMA / system catalog queries — these indicate an attacker enumerating the schema.
  • Out-of-band indicators: Successful SQL injection may cause the database server to make outbound DNS or HTTP requests (for exfiltration). Monitor for unexpected outbound connections from database hosts.
• T1210 — Exploitation of Remote Services
  • Monitor SMB, RDP, WinRM, SSH, and RPC activity between internal systems for patterns outside your normal management baseline.
  • Look for authentication bursts: repeated failures (Event ID 4625) from the same source followed by a successful logon (Event ID 4624).
  • Investigate remote execution behavior and lateral movement artifacts (PsExec, WMI remote execution, remote scheduled task creation) originating from recently exposed assets.

Hunting Considerations

These are proactive hunts mapped to the ATT&CK techniques identified for this CVE. Run them now — do not wait for an alert to fire.

• T1210 — Exploitation of Remote Services
  • Authentication burst pattern: Hunt for Event ID 4625 (failed logon) followed quickly by Event ID 4624 (successful logon) from the same source IP. This burst — repeated failures then success — is a classic exploitation indicator. Flag unusual Logon Type values: Type 3 (network), Type 10 (RemoteInteractive).
  • Unexpected east-west traffic: Look for new SMB (445), RDP (3389), WinRM (5985/5986), or SSH (22) connections between internal hosts that do not follow normal patterns — especially from workstations to servers or from servers outside your known management tooling.
  • Lateral movement artifacts: Hunt for PsExec service entries (Event ID 7045 with service name “PSEXESVC”), WMI remote execution (wmiprvse.exe spawning child processes), and scheduled tasks created via remote sessions (Event ID 4698).
  • Segmentation gaps: Confirm which affected hosts have network paths to domain controllers, file servers, or databases. Remote service exploitation is substantially more dangerous when segmentation is absent — validate this before concluding triage.
  • Unusual ports: Some exploitation of remote services uses non-standard ports. Cross-reference all new internal connections against your expected service port baseline to catch off-port lateral movement.

Recommended Actions

Immediate (0–24 Hours)

• Inventory: Identify all systems running Sangoma Switchvox. Include production, staging, dev, and cloud environments — untracked instances are the most likely to remain unpatched.
• Validate internet-facing exposure: Determine which of the affected systems are reachable from the public internet. Prioritize these for immediate remediation or compensating controls.
• Apply compensating controls now: For systems that cannot be patched immediately, implement temporary mitigations: restrict access via firewall rules or ACLs, add WAF rules if applicable, disable or isolate the vulnerable component if feasible without breaking critical operations.

Remediation

• Apply the vendor patch: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
• CISA directive deadline: 2026-09-05 — this is the mandatory deadline for US federal civilian agencies under BOD 22-01. All organizations should treat this date as a strong target regardless of federal mandate.
• Verify remediation: After patching, confirm the correct version is installed on all affected hosts. Run a vulnerability scan or use your asset management tooling to verify — do not rely solely on change tickets.
• Post-patch compromise assessment: Privilege escalation and lateral movement techniques can result in persistent access that survives patching. After remediation, review the hunting considerations in this alert to assess whether compromise occurred before the patch was applied.

Detection Coverage

• Verify ATT&CK coverage: Confirm your SIEM and EDR have detection logic in place for T1210. Review the Detection Guidance and Hunting Considerations sections of this alert for the specific log sources and behavioral patterns to monitor.
• Unauthenticated exploitation monitoring: Because this vulnerability requires no authentication, internet-facing scanning and exploitation attempts may begin within hours of public disclosure. Ensure alerting is in place before the end of the day.
• Threat intelligence feeds: Monitor your TI feeds and vendor advisory channels for published indicators of compromise (IOCs), proof-of-concept exploit releases, or active campaign reporting associated with this CVE — these should trigger an immediate hunt even if no internal alerts have fired.

Detection Playbooks

Vulnerability Details

Additional Notes

https://sangomakb.atlassian.net/wiki/spaces/Switchvox/pages/1802371073/Switchvox+-+Release+Notes+Version+8.4.0.2+July+14+2026 ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-9586