CVE-2025-55575: n/a
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% 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 25 Aug 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-26.
What to do
AI-suggested
Immediate mitigation steps include implementing web application firewalls (WAFs) with specific rules to detect and block SQL injection attempts targeting the action=service_detail parameter. Organizations should conduct thorough input validation and sanitization on all user-supplied data, especially in the affected module. Until an official patch is released, restricting access to the SMM Panel interface by IP whitelisting or VPN-only access can reduce exposure. Regularly monitoring logs for suspicious queries or unusual database activity is critical for early detection. Additionally, organizations should prepare for patch deployment by testing updates in isolated environments and ensure backups are current to enable recovery if exploitation occurs. Engaging with the vendor for timely patch releases and security advisories is also essential.
Description
SQL Injection vulnerability in SMM Panel 3.1 allowing remote attackers to gain sensitive information via a crafted HTTP request with action=service_detail.