CVE-2025-10105: yanyutao0402 ChanCMS · SQL Injection
Affects yanyutao0402 ChanCMSSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 8 Sep 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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| yanyutao0402 ChanCMS | Affected
| Fixed in– |
AI-suggested
Organizations should immediately identify all instances of ChanCMS version 3.3.0 and 3.3.1 in their environment. In the interim, implement web application firewall (WAF) rules to detect and block SQL injection patterns targeting the 'keyword' parameter in /cms/article/search requests. Conduct thorough input validation and sanitization on all user-supplied data, especially parameters used in database queries. Employ least privilege principles for database accounts used by ChanCMS to limit the impact of potential injection. Regularly monitor logs for suspicious activity related to SQL injection attempts. Additionally, consider isolating the CMS environment and restricting network access to trusted IPs where feasible. Finally, maintain an incident response plan to quickly address any exploitation attempts.
Description
A flaw has been found in yanyutao0402 ChanCMS up to 3.3.1. Affected by this issue is some unknown functionality of the file /cms/article/search. This manipulation of the argument keyword causes sql injection. The attack can be initiated remotely. The exploit has been published and may be used.