CVE-2025-15002: SeaCMS · SQL Injection
Affects SeaCMSSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 21 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SeaCMS | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-15002, organizations should immediately upgrade SeaCMS to a version where this vulnerability is patched once available. In the absence of an official patch, implement strict input validation and sanitization on the 'page' and 'limit' parameters to prevent injection of malicious SQL code. Employ parameterized queries or prepared statements in the affected PHP code to eliminate direct concatenation of user inputs into SQL commands. Restrict access to the CMS backend and related endpoints using network-level controls such as firewalls or VPNs to reduce exposure. Monitor web server and database logs for suspicious query patterns indicative of SQL injection attempts. Additionally, conduct regular security assessments and code reviews focusing on input handling. Deploy Web Application Firewalls (WAFs) with rules to detect and block SQL injection payloads targeting SeaCMS. Finally, maintain up-to-date backups of CMS data to enable recovery in case of data compromise.
Description
A vulnerability has been found in SeaCMS up to 13.3. The affected element is an unknown function of the file js/player/dmplayer/dmku/class/mysqli.class.php. Such manipulation of the argument page/limit leads to sql injection. The attack can be executed remotely. The exploit has been disclosed to the public and may be used.