CriticalPublic exploit

Unauthenticated Command Injection in VICIdial vicidial_sales_viewer.php

IdentifiersCVE-2025-34099CWE-78· Improper Neutralization of Special…

CVE-2025-34099 is an unauthenticated OS command injection vulnerability affecting VICIdial versions 2.9 RC1 through 2.13 RC1 in the vicidial_sales_viewer.php component, but only when password encryption is enabled, which is described as a non-default configuration. The vulnerable code path improperly passes the HTTP Basic Authentication password directly into a call to exec() without sufficient sanitization or neutralization of shell metacharacters. As a result, a remote attacker can supply crafted input in the Basic Authentication password field and cause arbitrary operating system commands to be executed by the underlying shell in the security context of the web server process. The issue is noted as having been mitigated in 2017.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows unauthenticated remote code execution as the web server user. This can enable full compromise of the affected application instance, theft or modification of VICIdial data, installation of additional malware or persistence mechanisms, pivoting to adjacent systems reachable from the host, and broader host-level impact depending on the privileges of the web server account and local hardening posture.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable VICIdial password encryption if operationally feasible, since the vulnerable condition requires that non-default setting to be enabled. Restrict or block access to vicidial_sales_viewer.php at the network or web-server layer, especially from untrusted networks. Enforce least privilege for the web server account to reduce post-exploitation impact, and monitor for suspicious requests using crafted HTTP Basic Authentication credentials or anomalous child processes spawned by the web server.

Remediation

Patch, then assume compromise.

Apply the vendor fix or upgrade to a VICIdial release in which the vulnerable exec()-based handling in vicidial_sales_viewer.php has been corrected. Because the issue is explicitly noted as mitigated in 2017, organizations should ensure they are not running affected historical builds from the 2.9 RC1 through 2.13 RC1 range without that mitigation. The vulnerable code path should be changed so that untrusted authentication data is never passed to exec() unsafely; if command execution is unavoidable, use strict input validation, parameterization, and shell-escaping-safe APIs, and remove direct shell invocation where possible.

PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app

vicidial_user_authorization_unauth_cmd_exec.rbMaturityWeaponizedFrameworkmetasploitVerified exploit

This repository contains a single Metasploit module targeting a command execution vulnerability in VICIdial versions 2.9 RC 1 to 2.13 RC1 (CVE-2025-34099). The exploit leverages a flaw in the user authorization process when password encryption is enabled, allowing unauthenticated attackers to execute arbitrary operating system commands as the web server user. The attack is performed by sending a specially crafted HTTP Basic Authentication password to the '/vicidial/vicidial_sales_viewer.php' endpoint. The module includes a check method to verify vulnerability and an exploit method that delivers the payload. The code is written in Ruby and is structured as a standard Metasploit exploit module, making it easy to use within the Metasploit framework. The exploit is operational and provides remote command execution capabilities, but requires the target to have password encryption enabled (not the default setting).

Disclosed May 26, 2017rubynetwork

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

VicidialVicidialapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

2 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2