Attackers Exploit Critical Sangoma Switchvox SQL Injection Flaw CVE-2026-9586 to Deploy Reverse Shells Without Credentials
Administrators of VoIP systems and IT security teams face an urgent new threat: a critical vulnerability in Sangoma Switchvox that enables remote code execution without any credentials. The flaw, identified as CVE-2026-9586 and rated CVSS 9.3, has already been exploited in real-world attacks to deploy reverse shells since August 30, 2026.
The vulnerability resides in the HTTP endpoint /pa, which processes XML requests. The system inserts the PhoneIP value directly into PostgreSQL queries without proper sanitization or parameterization. This classic CWE-89 SQL injection pattern allows attackers to run arbitrary database commands and escalate to full system command execution with PostgreSQL superuser privileges.
Observed attack activity includes the immediate opening of reverse shells and basic reconnaissance. Attackers use Base64-encoded commands to enumerate running processes and map the compromised server environment. One IP address linked to the campaign is 176.65.148.184. Forensic traces may appear in the log file /var/log/switchvox/db-quirks.log, which records attempted SQL injections and subsequent actions.
Patch Availability and Timeline
Sangoma released the corrective update in Switchvox 8.4.0.2 on July 14, 2026. The patch addresses the injection flaw along with additional web portal fixes. The disclosure timeline shows the initial report to the vendor on April 10, 2026, the patch release in mid-July, and confirmed exploitation by late August.
Thousands of Switchvox instances remain reachable from the internet, with a notable concentration in the United States. Organizations should prioritize immediate upgrades to version 8.4.0.2 or later, especially for any deployments exposed to untrusted networks.
Recommended Mitigations and Detection
- Apply the Switchvox 8.4.0.2 update without delay.
- Restrict access to the HTTP service using network segmentation, VPNs, or access control lists until patching is complete.
- Monitor outbound connections for anomalies, particularly attempts to reach 176.65.148.184 or the use of tools such as nc and unexpected bash invocations from web services.
- Inspect logs for signs of post-exploitation and rotate all associated credentials if compromise is suspected.
Additional technical details are available from The Hacker News and Horizon3.ai research reports, as well as official Sangoma release notes.
Related articles
How Modern API Attacks Abuse Legitimate Functionality Instead of Exploiting Vulnerabilities
Traditional API incidents once centered on authorization errors, access control issues, SQL injections, and known vulnerability exploitation. Today, many attacks on APIs no longer require finding code flaws; attackers simply use documented methods, valid authorization, and correct parameters at unexpected scale or timing. NGENIX security teams observe three main behavioral patterns: Burst attacks that overload resource-heavy endpoints, Shortwave attacks that exploit race conditions through timed parallel requests, and Carpet Bombing that distributes activity across dozens of endpoints for reconnaissance or scalping. These techniques often bypass WAF because each individual request appears fully compliant with API specifications. Protection is shifting toward behavioral analysis, sliding-window rate limiting, and monitoring of overall client behavior rather than single-request signatures. Real-world cases include sudden catalog scraping during contests and mass reservation of airline seats without purchases, leading to degraded service for legitimate users.
Critical Vulnerabilities Patched in WHMCS Billing Software for Hosting Providers
WebPros International has disclosed two serious vulnerabilities in its WHMCS billing management platform used by hosting and cloud service providers. CVE-2026-67399 allows unauthenticated remote code execution through unsafe deserialization of untrusted data under specific conditions, potentially compromising the entire server environment and associated data. CVE-2026-67398 affects the 2CheckOut payment gateway module and stems from missing authorization checks, enabling attackers to retrieve sensitive customer information including names, addresses, emails, and phone numbers without authentication. HackerOne assigned CVSS v4.0 scores of 9.3 (Critical) to the first issue and 8.2 (High) to the second. WebPros released fixed versions WHMCS 9.0.8 and 8.13.7, and recommended disabling the 2CheckOut module as a temporary mitigation for the second flaw.
Cisco Releases Critical Patches for Exploited SQL Injection Flaw in Secure Email Gateway
Cisco Systems has issued security updates for Cisco Secure Email Gateway to address a critical SQL injection vulnerability tracked as CVE-2026-76461. The flaw stems from insufficient input validation during email parsing and allows unauthenticated remote attackers to execute arbitrary SQL commands. Successful exploitation can lead to root-level access on the underlying operating system, enabling full command execution. The vulnerability carries a CVSSv3.1 base score of 9.8 and is rated Critical. Cisco confirmed active exploitation of the issue in September 2026. Recommended fixes include upgrading to versions 16.5.0-780, 16.0.4-3021, or 15.5.5-0141, with strong preference given to the newest release.
Telegram Desktop HTML Export Flaw Allowed Stealthy JavaScript Injection into Chat History
Researchers at ExPatch identified a vulnerability in Telegram Desktop that enabled attackers to embed malicious JavaScript into exported HTML chat histories without user detection. The flaw stemmed from insufficient sanitization of button captions added by bots, allowing hidden scripts to execute when the HTML file was opened in a browser. Malicious messages could be forwarded into chats and remain dormant until export, potentially exfiltrating messages, sender names, and timestamps to attacker servers. The issue affected versions 4.15.1 through 6.9.3, with fixes released in beta 6.9.4 and stable version 7.0.1 on July 14. No in-the-wild exploitation was observed, though the attack required specific conditions including an unpatched export and JavaScript-enabled browser. Users are advised to re-export chats after updating or open old files with JavaScript disabled.