CVE-2025-14730: CTCMS Content Management System · Code Injection
Affects CTCMS Content Management SystemSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 15 Dec 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 |
|---|---|---|
| CTCMS Content Management System | Affected
| Fixed in– |
AI-suggested
1. Immediately restrict access to the Backend System Configuration Module and the /ctcms/libs/Ct_Config.php file to only highly trusted and authenticated users, ideally through network segmentation and strong access controls. 2. Monitor web server and application logs for unusual or unauthorized requests involving the Cj_Add and Cj_Edit parameters, setting up alerts for suspicious activity. 3. Implement Web Application Firewall (WAF) rules to detect and block attempts to inject code via these parameters, using pattern matching and anomaly detection. 4. Conduct a thorough review of user privileges to ensure that only necessary users have backend access, reducing the risk of privilege abuse. 5. 6. Perform regular security assessments and penetration tests focusing on the CMS backend to identify and remediate similar vulnerabilities. 7. Educate administrators and developers about secure coding practices and the risks of code injection to prevent recurrence. 8. Maintain up-to-date backups of CMS data and configurations to enable rapid recovery in case of compromise.
Description
A security flaw has been discovered in CTCMS Content Management System up to 2.1.2. The impacted element is an unknown function in the library /ctcms/libs/Ct_Config.php of the component Backend System Configuration Module. The manipulation of the argument Cj_Add/Cj_Edit results in code injection. The attack can be executed remotely. The exploit has been released to the public and may be exploited.