CVE-2025-14730
BaseFortify
Publication date: 2025-12-15
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ctcms_project | ctcms | to 2.1.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for unauthorized or suspicious modifications in the file `/ctcms/libs/Ct_Config.php`, as it may contain injected PHP code. Additionally, monitoring HTTP requests to the backend system configuration module for suspicious parameters such as `Cj_Add` or `Cj_Edit` carrying PHP code payloads can help detect exploitation attempts. A suggested method is to use Google dorking with the query `inurl:ctcms/libs/Ct_Config.php` to identify vulnerable targets. Network monitoring tools can be used to capture and inspect HTTP POST requests to the configuration endpoints for suspicious payloads. Specific commands are not provided, but searching for PHP code injection patterns in the configuration file or intercepted requests is recommended. [2, 1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting and monitoring authenticated administrator access to the backend system configuration module to prevent unauthorized configuration changes. Since the vulnerability arises from improper input sanitization when writing configuration data to `/ctcms/libs/Ct_Config.php`, avoid using the affected version (up to 2.1.2) or replace the affected component with an alternative product. No known countermeasures or patches are reported, so limiting access and monitoring for suspicious activity are critical. Additionally, reviewing and sanitizing input parameters such as `Cj_Add` and `Cj_Edit` before saving configuration data can help prevent exploitation. [2, 1]
Can you explain this vulnerability to me?
This vulnerability is a security flaw in the CTCMS Content Management System up to version 2.1.2, specifically in an unknown function within the Backend System Configuration Module's library file /ctcms/libs/Ct_Config.php. It involves manipulation of the argument Cj_Add/Cj_Edit, which leads to code injection. This means an attacker can remotely execute malicious code on the affected system.
How can this vulnerability impact me? :
The vulnerability allows remote attackers to inject and execute arbitrary code on the affected system. This can lead to unauthorized access, data compromise, system disruption, or further exploitation of the system's resources.