CVE-2022-50795
Sound4 First Firmware command injection
- Published30 Dec 2025
Description
SOUND4 IMPACT/FIRST/PULSE/Eco <=2.x contains a conditional command injection vulnerability that allows local authenticated users to create malicious files in the /tmp directory. Unauthenticated attackers can execute commands by making a single HTTP POST request to the traceroute.php script, which triggers the malicious file and then deletes it after execution.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://exchange.xforce.ibmcloud.com/vulnerabilities/247950
- https://packetstormsecurity.com/files/170267/SOUND4-IMPACT-FIRST-PULSE-Eco-2.x-traceroute.php-Conditional-Command-Injection.html
- https://www.sound4.com/
- https://www.vulncheck.com/advisories/sound-impactfirstpulseeco-x-conditional-command-injection-via-traceroutephp
- https://www.zeroscience.mk/en/vulnerabilities/ZSL-2022-5740.php
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2022-50795 being actively exploited?
CVE-2022-50795 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 4.16%.
How severe is CVE-2022-50795?
CVE-2022-50795 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 4.16% probability of exploitation.
Which products are affected by CVE-2022-50795?
Affected products include Sound4 Stream Extension, Sound4 Big Voice2 Firmware, Sound4 Big Voice4 Firmware, Sound4 First Firmware, Sound4 Impact Eco Firmware, and 4 more.
How do I fix CVE-2022-50795?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2022-50795 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.