CVE-2025-11903VulnerabilityPublished 17 Oct 2025Updated 24 Feb 2026

CVE-2025-11903: 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

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% 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 17 Oct 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.

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 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
GitHubyanyutao0402/ChanCMS`pkg:github/yanyutao0402/ChanCMS`Other threats	Affected =3.3.0 =3.3.1 =3.3.2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of official patches, organizations should implement immediate compensating controls. First, restrict access to the /cms/article/update endpoint using web application firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'cid' parameter. Employ input validation and sanitization at the application or proxy level to reject suspicious input. Monitor web server and application logs for unusual query parameters or error messages indicative of injection attempts. If feasible, isolate the CMS environment from critical internal networks to limit lateral movement in case of compromise. Regularly back up CMS data and test restoration procedures to mitigate data loss. Organizations should also consider migrating to alternative CMS platforms or earlier/later versions not affected by this vulnerability until an official patch is released. Engage in threat intelligence sharing to stay informed about emerging exploits targeting this vulnerability.

Description

A flaw has been found in yanyutao0402 ChanCMS up to 3.3.2. Affected by this issue is the function update of the file /cms/article/update. Executing a manipulation of the argument cid can lead to sql injection. The attack can be launched remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The SQL injection vulnerability in ChanCMS can have significant consequences for organizations relying on this CMS platform. Attackers exploiting this flaw can gain unauthorized access to sensitive information stored in the database, including user credentials, content, and configuration data. They may also modify or delete data, disrupting website operations and causing data integrity issues. The ability to execute arbitrary SQL commands remotely without authentication increases the risk of automated attacks and large-scale exploitation. This can lead to data breaches, defacement, loss of customer trust, and potential regulatory penalties. Additionally, compromised CMS platforms can serve as footholds for further network intrusion or malware deployment. Organizations with public-facing ChanCMS installations are particularly vulnerable, especially if they have not implemented additional security controls or monitoring.

Summary

CVE-2025-11903 identifies a SQL injection vulnerability in the ChanCMS content management system, specifically in versions 3.3.0 through 3.3.2. The vulnerability resides in the update function located at /cms/article/update, where the 'cid' parameter is improperly sanitized, allowing an attacker to inject malicious SQL code. This injection flaw enables remote attackers to manipulate backend database queries, potentially extracting sensitive data, altering database records, or causing denial of service. The attack vector requires no authentication or user interaction, increasing the ease of exploitation. The CVSS 4.0 base score is 5.3 (medium), reflecting moderate impact and exploitability. Despite early vendor notification, no patches or official responses have been issued, and a public exploit is available, raising the risk of future attacks. The vulnerability affects the confidentiality, integrity, and availability of the CMS data, with a low attack complexity and no privileges required. The lack of vendor response and patch availability necessitates immediate attention from users of ChanCMS.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 21:33 UTC

Technical details

References

Community reviews

Related threats