Summary
SeaCMS contains a SQL injection vulnerability in the video-list API when processing the ids argument. A remote attacker may be able to manipulate database queries, potentially accessing, modifying, or disrupting stored data when the affected endpoint is reachable and input is not safely handled.
Affected context
The issue affects SeaCMS deployments up to version 13.6 where the /zyapi.php?ac=videolist functionality processes the ids parameter. Risk depends on whether the endpoint is exposed to an attacker, whether authentication or access controls are enforced, and whether user-controlled values reach database queries without adequate separation from SQL syntax.
Exploit preconditions
- Attack surface: The remotely accessible
/zyapi.php?ac=videolistendpoint - Required access: Network access to the endpoint; authentication requirements depend on the deployment configuration
- Trigger point: Processing of the
idsargument in a video-list request - Why exploitation is possible: Insufficient separation between externally supplied input and the SQL statement may allow input to alter query behavior
Why this happens
The underlying bug is improper neutralization of special elements in database queries. When the ids parameter is incorporated into SQL without parameterized query handling or equivalent strict controls, attacker-controlled content may be interpreted as SQL syntax rather than data. This maps primarily to CWE-89: Improper Neutralization of Special Elements used in an SQL Command (SQL Injection) and is also related to CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component.
Potential impact
- An attacker may read information from application databases
- An attacker could alter or delete stored records
- Database integrity may be compromised
- The application may experience service disruption
- Exposed credentials or sensitive data could enable further compromise
General mitigation guidance
Mitigation generally focuses on ensuring that database commands treat external values strictly as data.
Common defensive patterns include:
- Using parameterized queries or prepared statements for all database operations
- Applying allowlisted validation for identifier-like values such as video IDs
- Avoiding string concatenation when constructing SQL statements
- Enforcing authentication and authorization at the API boundary
- Limiting the database account to the minimum required privileges
- Preventing detailed database errors from being returned to clients
- Separating application, reporting, and administrative database permissions where practical
How teams detect issues like this
Organizations can identify SQL injection risks through:
- Static analysis rules for SQL string concatenation and dynamic query construction
- Code review checks for request parameters reaching database APIs
- Dynamic testing of API inputs using controlled, non-destructive test cases
- Web-application firewall or API-gateway policies for anomalous query parameters
- Database monitoring for unexpected query shapes, error spikes, or unusual read and write activity
- Automated security review tools that flag unparameterized database access

