Skip to main content
VulnerabilityPublished Updated

CVE-2025-65602: ChanCMS · A Template Injection

Affects ChanCMSSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubchancms/ChanCMSpkg:github/chancms/ChanCMSOther threatsAffected
  • =3.3.4
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, European organizations should implement immediate compensating controls. First, restrict network access to the /vip/v1/file/save endpoint using web application firewalls (WAFs) or network access controls to limit exposure to trusted IP addresses only. Deploy WAF rules that detect and block suspicious POST requests containing template injection patterns or unusual payloads. Conduct thorough logging and monitoring of web server and application logs to identify anomalous activities targeting this endpoint. Employ intrusion detection systems (IDS) with updated signatures to detect exploitation attempts. If possible, temporarily disable or restrict the vulnerable component until a patch is available. Organizations should also review and harden template rendering configurations to minimize injection risks. Prepare for rapid patch deployment by maintaining close communication with ChanCMS vendors or community channels for updates. Additionally, conduct internal vulnerability scans and penetration tests to identify any signs of compromise. Educate development and operations teams about this vulnerability to ensure awareness and prompt response.

Description

A template injection vulnerability in the /vip/v1/file/save component of ChanCMS v3.3.4 allows attackers to execute arbitrary code via a crafted POST request.

References

Community reviews

Loading reviews…