Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-75330 – SQL Injection – super-diamond-server ≤ 1.3.3

Be the first to know when new zero-days emerge:

Summary

CVE-2026-75330 is a critical SQL injection vulnerability affecting super-diamond-server versions 1.3.3 and earlier. The flaw resides in the module path parameter of the front-end preview interface, which is concatenated directly into a SQL IN clause without parameterization, allowing an attacker to inject arbitrary SQL. The issue carries a CVSS v3.1 base score of 9.8 (Critical), reflecting its network-exploitability and potential for full compromise of data confidentiality, integrity, and availability.

Technical details

  • Root cause: The vulnerable endpoint builds a SQL IN clause by splitting the module parameter with StringUtils.split() and concatenating the resulting values directly into the query string inside ConfigDaoImpl.java, instead of using parameterized/bound statements.
  • Bypassed protection: super-diamond-server ships with a built-in SqlInjectionUtil sanitization helper, but this code path never invokes it, leaving the parameter fully exposed to injection.
  • Trigger conditions: An HTTP GET request to /superdiamond/preview/{projectCode}/{module}/{type} with a crafted module value (e.g., a payload containing ' ) OR 1=1--) triggers the injected SQL logic. Public proof-of-concept exploitation demonstrated a session cookie (JSESSIONID) associated with a valid application login (documented as the product’s default admin/000000 account) being sufficient to reach the vulnerable code path.
  • Attack vector: Network-based (AV:N), no user interaction required (UI:N); the CVE’s published CVSS vector specifies no privileges required (PR:N).
  • Impact: Full impact to confidentiality, integrity, and availability (C:H/I:H/A:H). Publicly documented exploitation extracted database version information and an administrator’s unsalted MD5 password hash from the CONF_USER table via UNION-based injection, and the technique could be extended to stacked queries against the underlying database.

Affected software

  • super-diamond-server: all versions ≤ 1.3.3

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade super-diamond-server to a version newer than 1.3.3 that parameterizes the module value in the preview endpoint’s SQL IN clause (or confirm with the vendor that the affected code path has been fixed and routed through the existing SqlInjectionUtil sanitizer).
  • If no patch is available:
    • Restrict network access to the /superdiamond/preview/{projectCode}/{module}/{type} endpoint to trusted internal networks only; do not expose it directly to the internet.
    • Change any default credentials (including the documented default admin/000000 account) and enforce strong, unique credentials for all accounts able to reach the application.
    • Deploy a web application firewall (WAF) rule to detect and block SQL metacharacters and injection patterns in the module path segment.
    • Monitor database and application logs for anomalous queries against configuration/user tables (e.g., CONF_USER) and for unexpected UNION-based query patterns.
    • Rotate credentials and password hashes for any accounts that may have been exposed if the endpoint has been internet-facing.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge