# CVE-2026-82598: SeaCMS template engine code injection in search.php

Source: https://junglewise.ai/threats/cve-2026-82598-seacms-template-engine-code-injection-in-search-php  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-31. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-82598 · Severity: high · CVSS 7.3 · Published 2026-08-31

SeaCMS is a content management system with a template engine used to render search results. A flaw in the search function allows attackers to inject arbitrary code into template expressions, leading to remote code execution on the server with the privileges of the web server process.

Technologies: [Seacms](https://junglewise.ai/threats/technologies/seacms). Vendors: [Seacms](https://junglewise.ai/threats/vendors/seacms).

## Quick answers

**Is CVE-2026-82598 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-82598 being exploited in the wild.

**How severe is CVE-2026-82598?** 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-82598?** 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-82598 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-82598?** 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

The vulnerability is a server-side template injection (SSTI) in the search.php component. When processing searchtype=5 requests, user-controlled parameters (such as 'area' and 'yuyan') are substituted directly into template {if:...} conditional expressions without sanitization. The template engine's parseIf() function in include/main.class.php then evaluates these expressions using PHP eval(), allowing attackers to inject arbitrary PHP code. No authentication is required and attack can be executed remotely via GET requests. Attackers can achieve remote code execution with the privileges of the web server process (typically www-data). Proof-of-concept exploits demonstrate command execution via PHP backtick syntax (e.g., ?searchtype=5&area=print%60id%60). The vulnerability has been publicly disclosed and no official patch status is stated.

## Affected products

- SeaCMS SeaCMS up to 13.6

## Timeline

- 2026-08-31: disclosed
- other: Exploit publicly available via GitHub security advisories

## References

- [https://github.com/T-Chachamaru/seacms-13.6-security-advisories/blob/a084a3e573240d54860153321df271280daec262/c-009-search-cascade-template-rce.md](https://github.com/T-Chachamaru/seacms-13.6-security-advisories/blob/a084a3e573240d54860153321df271280daec262/c-009-search-cascade-template-rce.md)
- [https://vuldb.com/cve/CVE-2026-82598](https://vuldb.com/cve/CVE-2026-82598)

## Related threats

- [SeaCMS SQL injection in comment API](https://junglewise.ai/threats/cve-2019-25778-seacms-through-8-7-contains-an-unauthenticated-sql-injection)
- [SeaCMS authenticated remote code execution in admin_config.php](https://junglewise.ai/threats/cve-2026-79423-seacms-authenticated-remote-code-execution-in-admin-config-php)
- [SeaCMS WeChat Module SQL injection via XML entity decoding](https://junglewise.ai/threats/cve-2026-85138-seacms-wechat-module-sql-injection-via-xml-entity-decoding)
- [SeaCMS Locoy Collector code injection via default password](https://junglewise.ai/threats/cve-2026-85137-seacms-locoy-collector-code-injection-via-default-password)
- [SeaCMS path traversal in member.php comment deletion](https://junglewise.ai/threats/cve-2026-82603-seacms-path-traversal-in-member-php-comment-deletion)