CVE-2025-50475: Russound MBX-PRE-D67F firmware · OS Command Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 7.7% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 31 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2025-50475, European organizations should immediately identify and isolate all Russound MBX-PRE-D67F devices running firmware version 3.1.6. Employ network intrusion detection systems (NIDS) to monitor for suspicious or malformed network configuration requests targeting the hostname parameter. Disable remote management features if not required, or enforce strict access controls and VPN usage for remote administration. Organizations should also engage with Russound support channels to obtain information on forthcoming patches or mitigations and plan for timely firmware updates once available. As a longer-term measure, consider replacing vulnerable devices with models that have robust security controls and input validation. Additionally, conduct regular security audits of IoT and networked audio devices to detect anomalous behavior indicative of compromise.
Description
An OS command injection vulnerability exists in Russound MBX-PRE-D67F firmware version 3.1.6, allowing unauthenticated attackers to execute arbitrary commands as root via crafted input to the hostname parameter in network configuration requests. This vulnerability stems from improper neutralization of special elements used in an OS command within the network configuration handler, enabling remote code execution with the highest privileges.