CVE-2025-63220: n/a
Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 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 2026-10-25.
What to do
AI-suggested
Organizations should immediately restrict access to the firmware update interface to trusted administrators only, employing strong authentication and network segmentation. Implement strict validation of firmware packages by verifying digital signatures or checksums before applying updates to ensure integrity. Monitor firmware update activities and system logs for any unauthorized or suspicious changes to manual.sh or related scripts. If possible, disable manual firmware updates temporarily until a patch or official guidance is released by the vendor. Engage with Sound4 FIRST support channels to obtain updates or patches addressing this vulnerability. Conduct regular security audits of device configurations and update mechanisms. Consider deploying intrusion detection systems capable of identifying anomalous command executions or firmware modifications. Finally, maintain an incident response plan tailored to potential device compromise scenarios.
Description
The Sound4 FIRST web-based management interface is vulnerable to Remote Code Execution (RCE) via a malicious firmware update package. The update mechanism fails to validate the integrity of manual.sh, allowing an attacker to inject arbitrary commands by modifying this script and repackaging the firmware.