Quick answers
- Is CVE-2026-82600 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82600 being exploited in the wild.
- How severe is CVE-2026-82600?
- High severity, with a CVSS score of 7.3, published 31 August 2026.
- Which products and versions are affected?
- Seacms up to 13.6.
- Is there a fix for CVE-2026-82600?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-82600 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-82600?
- Check whether you run Seacms at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
SeaCMS 13.6 contains a SQL injection vulnerability in zyapi.php where the ids parameter is passed to an SQL IN clause after only addslashes() sanitization, without strict integer validation. The vulnerability exists because the parameter is interpreted as a SQL numeric expression rather than a validated comma-separated integer list, allowing attackers to inject arithmetic and SQL expressions (e.g., ids=2+1). No authentication or user interaction is required; the attack is remotely exploitable via HTTP GET request. An attacker can manipulate database queries to extract sensitive information, though UNION-based payloads and direct data exfiltration are restricted by the IN clause context. Remediation requires strict integer validation with intval() casting and parameterized queries rather than string concatenation.
Affected products
- SeaCMS SeaCMS up to 13.6
Timeline
- 2026-08-31: disclosed