CVE-2025-15129
Remote Code Injection in Lin-CMS-TP5 File Upload Handler
Publication date: 2025-12-28
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 |
|---|---|---|
| chenjinchuang | lin-cms-tp5 | 0.3.3 |
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 is a flaw in the Upload function of the file application/lib/file/LocalUploader.php in ChenJinchuang Lin-CMS-TP5 up to version 0.3.3. It allows an attacker to manipulate the File argument to inject code remotely, potentially executing malicious code on the server.
How can this vulnerability impact me? :
The vulnerability can lead to remote code injection, which may allow an attacker to execute arbitrary code on the affected system. This can compromise the integrity, confidentiality, and availability of the system and its data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows remote code execution, persistent backdoors, and information leakage, it could potentially lead to unauthorized access or disclosure of sensitive data, which may violate data protection regulations. No direct statements about compliance impact are available in the provided texts. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the vulnerable endpoint POST /cms/file is accessible and allows uploading files without proper validation. You can attempt to upload a test file with a script extension (e.g., test.php) to the /cms/file endpoint and then verify if the file is saved in the public/uploads directory and can be accessed/executed via a URL. For example, you can use curl to send a crafted multipart/form-data POST request to upload a PHP file: curl -X POST -F "[email protected]" http://target/cms/file Then check if the file is accessible via a URL like http://target/uploads/<date>/<filename>.php. Additionally, you can search your system for uploaded files with executable extensions in the public/uploads directory. Also, attackers may use Google dorking with queries like inurl:application/lib/file/LocalUploader.php to identify vulnerable targets. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or disabling the file upload functionality at the /cms/file endpoint if possible. Implement strict validation and filtering of uploaded files to allow only safe file types and sanitize filenames. Restrict execution permissions on the public/uploads directory to prevent execution of uploaded scripts. If no patch or fix is available, consider replacing the affected product with an alternative CMS. Monitoring and blocking suspicious upload attempts can also help reduce risk. [1, 2, 3]