Command execution via malicious traceroute PID file
Published Dec 30, 2025 · Updated Dec 30, 2025
Command injection in SOUND4 BIG VOICE 2 1.30, BIG VOICE 4 1.2, and WM2 1.11 allows attackers to execute system commands. The traceroute.php script executes commands stored in a /tmp filename ending in .traceroute.pid after one HTTP POST request, then deletes the file. A local authenticated user must first create the malicious file; a remote unauthenticated attacker can then trigger one-time command execution and service interruption.
Summary
What happened
Command injection in SOUND4 BIG VOICE 2 1.30, BIG VOICE 4 1.2, and WM2 1.11 allows attackers to execute system commands. The traceroute.php script executes commands stored in a /tmp filename ending in .traceroute.pid after one HTTP POST request, then deletes the file. A local authenticated user must first create the malicious file; a remote unauthenticated attacker can then trigger one-time command execution and service interruption.
The record
- CVE
- CVE-2022-50795
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- Kantar Media
- Product
- BIG VOICE 2
- Classifications
- CWE-78, T1059
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.30
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- sound4_traceroute_cmdinj.txtproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo