CVE-2026-75330: super-diamond-server · SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Affects
- super-diamond-server up to 1.3.3
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 26 Aug 2026
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
Until an official fix is available, users should avoid exposing the vulnerable endpoint to untrusted inputs or implement application-layer input validation and parameterized queries as a temporary mitigation.
Description
A SQL injection vulnerability exists in the front-end interface /superdiamond/preview/{projectCode}/{module}/{type} of super-diamond-server versions up to and including 1.3.3. The vulnerability arises because the module parameter is concatenated directly into an SQL IN clause without proper parameterization or binding, allowing potential injection of malicious SQL code. This vulnerability has a critical severity with a CVSS score of 9.8.