CVE-2025-15002

7.3

SeaCMS · SeaCMS

A SQL injection vulnerability in SeaCMS versions 13.0 through 13.3 allows remote, unauthenticated attackers to manipulate database queries via the page or limit arguments in mysqli.class.php.

Executive summary

SeaCMS versions 13.0 through 13.3 are vulnerable to a remote SQL injection attack, which could allow unauthorized database interaction.

Vulnerability

This is a SQL injection vulnerability (CWE-89) located in the mysqli.class.php file. An unauthenticated remote attacker can trigger this flaw by sending a crafted request to the application, manipulating the page or limit parameters to execute arbitrary SQL commands.

Business impact

The vulnerability carries a CVSS score of 7.3, reflecting a high-severity risk due to the lack of required authentication. Successful exploitation may lead to unauthorized data access, potential modification of database contents, or unauthorized information disclosure, which can cause significant reputational damage and regulatory non-compliance.

Remediation

Immediate Action: Since no specific patch version is currently confirmed, administrators should restrict access to the vulnerable endpoint or contact the vendor for immediate security guidance.

Proactive Monitoring: Review web server access logs for anomalous requests containing SQL syntax patterns or unexpected input in the page and limit parameters.

Compensating Controls: Deploy a Web Application Firewall (WAF) with updated rulesets designed to detect and block common SQL injection payloads targeting the identified parameters.

Exploitation status

Public Exploit Available: Yes — a published proof-of-concept exists, as documented in the technical write-up referenced by the CVE record.

Analyst recommendation

Given the availability of a public proof-of-concept and the ease of exploitation, this vulnerability presents a credible risk to the integrity of the backend database. Organizations should treat this as a priority and implement stringent input validation or WAF filtering immediately to prevent unauthorized access while awaiting a vendor-provided security update.

Sources

Originally found and disclosed by yu22x (VulDB User), per the CVE Program record.