CVE-2025-14729
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
Can you explain this vulnerability to me?
This vulnerability exists in the CTCMS Content Management System up to version 2.1.2, specifically in the Save function of the Backend App Configuration Module. It involves manipulation of the CT_App_Paytype argument, which leads to code injection. This means an attacker can remotely execute malicious code on the system by exploiting this flaw.
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 manipulation, or disruption of service, potentially compromising the confidentiality, integrity, and availability of the system and its data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable file `/ctcms/libs/Ct_App.php` and monitoring for suspicious modifications to this file, especially changes to the `CT_App_Paytype` parameter in the backend APP configuration. Additionally, attackers may be identified by searching for attempts to exploit the vulnerability using Google dorking with queries like `inurl:ctcms/libs/Ct_App.php`. Network detection could involve monitoring for unusual HTTP POST requests to the backend APP configuration page that include the `CT_App_Paytype[]` parameter with suspicious payloads. Specific commands to detect exploitation attempts include using web server logs to grep for `CT_App_Paytype` or scanning the file for injected PHP code. For example, on the server, you could run: `grep -r "CT_App_Paytype" /ctcms/libs/Ct_App.php` or check web server logs with `grep "CT_App_Paytype" /var/log/httpd/access_log` (paths may vary). [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the backend APP configuration module to trusted administrators only, monitoring and auditing changes to the `CT_App_Paytype` parameter, and avoiding use of the vulnerable CTCMS version up to 2.1.2. Since no known countermeasures or patches are published, it is recommended to replace or upgrade the affected component or product to a non-vulnerable version if available. Additionally, reviewing and sanitizing input handling in the backend configuration module to prevent code injection is advised. Limiting privileges of authenticated users to prevent unauthorized configuration changes can also reduce risk. [1, 2]