Skip to main content
VulnerabilityPublished Updated

CVE-2025-11904: yanyutao0402 ChanCMS · SQL Injection

Affects yanyutao0402 ChanCMSSource CVE Database V5

0

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
GitHubyanyutao0402/ChanCMSpkg:github/yanyutao0402/ChanCMSOther threatsAffected
  • =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

Organizations using ChanCMS versions 3.3.0 through 3.3.2 should immediately audit their installations for exposure to this vulnerability. 2) Restrict network access to the CMS backend to trusted IP addresses where feasible, reducing exposure to remote attackers. 3) Conduct thorough input validation and sanitization at the application or database layer if possible, applying parameterized queries or prepared statements to prevent injection. 4) Monitor logs for unusual database queries or error messages indicative of injection attempts. 5) Plan for an upgrade or migration to a patched or alternative CMS solution once available. 6) Regularly back up CMS data to enable recovery in case of data corruption or loss. 7) Educate administrators about the vulnerability and encourage vigilance against suspicious activity. These steps provide layered defense until an official patch or update is released by the vendor.

Description

A vulnerability has been found in yanyutao0402 ChanCMS up to 3.3.2. This affects the function hasUse of the file /cms/model/hasUse. The manipulation of the argument ID leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

References

Community reviews

Loading reviews…