VulnerabilityPublished 8 Sep 2025

CVE-2025-10106: yanyutao0402 ChanCMS · SQL Injection

Affects yanyutao0402 ChanCMSSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% 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:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
yanyutao0402 ChanCMS	Affected =3.3.0 =3.3.1	Fixed in–

AI-suggested

Organizations should immediately audit their use of ChanCMS to identify if versions 3.3.0 or 3.3.1 are deployed. Until an official patch is released, applying web application firewall (WAF) rules to detect and block SQL injection patterns targeting the 'keyword' parameter in the /cms/collect/search endpoint is critical. Input validation and sanitization should be enforced at the application level, employing parameterized queries or prepared statements if source code access is available. Monitoring web server logs for suspicious query patterns and unusual database errors can help detect attempted exploitation. Restricting database user permissions to the minimum necessary can limit the impact of a successful injection. Organizations should also consider isolating the CMS environment and conducting penetration testing to assess exposure. Finally, maintain readiness to apply vendor patches promptly once available and update incident response plans to address potential exploitation scenarios.

Description

A vulnerability has been found in yanyutao0402 ChanCMS up to 3.3.1. This affects an unknown part of the file /cms/collect/search. Such manipulation of the argument keyword leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using ChanCMS versions 3.3.0 or 3.3.1, this vulnerability could lead to unauthorized data access, data tampering, or service disruption. Given that CMS platforms often manage website content, user information, and sometimes transactional data, exploitation could result in data breaches, defacement, or loss of trust from customers and partners. Organizations in sectors such as media, education, government, and SMEs that rely on ChanCMS for web presence are particularly at risk. The remote and unauthenticated nature of the attack increases the likelihood of exploitation, potentially leading to regulatory non-compliance under GDPR if personal data is exposed. Additionally, compromised CMS instances could be leveraged as footholds for further network intrusion or to distribute malware, amplifying the security impact.

Summary

CVE-2025-10106 is a SQL Injection vulnerability identified in the yanyutao0402 ChanCMS content management system, specifically affecting versions 3.3.0 and 3.3.1. The vulnerability resides in the /cms/collect/search endpoint, where the 'keyword' parameter is improperly sanitized, allowing an attacker to inject malicious SQL code. This flaw enables remote exploitation without requiring user interaction or authentication, as indicated by the CVSS vector (AV:N/AC:L/AT:N/UI:N/PR:L). The vulnerability impacts confidentiality, integrity, and availability of the backend database, potentially allowing attackers to extract sensitive data, modify or delete records, or disrupt CMS functionality. Although the CVSS score is moderate at 5.3, the exploitability is relatively straightforward due to low attack complexity and no need for user interaction. No official patches or fixes have been published yet, and no known exploits are currently reported in the wild. However, public disclosure of the exploit code increases the risk of opportunistic attacks. The vulnerability's partial impact on confidentiality, integrity, and availability (labeled as low in each) suggests that while the damage may be limited compared to more severe SQL injections, it still poses a significant threat to affected systems, especially those handling sensitive content or user data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Sep 2025, 01:04 UTC

Technical details

References

Community reviews

Related threats