CVE-2025-7878
BaseFortify
Publication date: 2025-07-20
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 |
|---|---|---|
| metasoft | metacrm | to 6.4.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-434 | The product allows the upload or transfer of dangerous file types that are automatically processed within its environment. |
| CWE-284 | The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to server compromise, allowing attackers to execute malicious activities such as running arbitrary code, accessing sensitive data, or disrupting services. This impacts the confidentiality, integrity, and availability of the affected system, potentially causing significant operational and security issues. [1, 2]
Can you explain this vulnerability to me?
CVE-2025-7878 is an unrestricted file upload vulnerability in Metasoft MetaCRM versions up to 6.4.2, specifically in the /common/jsp/upload2.jsp file. The vulnerability arises because the application improperly restricts the 'File' argument, allowing attackers to upload arbitrary files without limitation. This can be exploited remotely and enables attackers to potentially compromise the server by uploading malicious files. [1, 2]
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 upload interface at /common/jsp/upload2.jsp. Attackers may use Google dorking with the query 'inurl:common/jsp/upload2.jsp' to find vulnerable targets. On your system, you can attempt to access or scan for this URL path on your MetaCRM server. Additionally, monitoring for unexpected file uploads or suspicious HTTP POST requests to /common/jsp/upload2.jsp may help detect exploitation attempts. Specific commands could include using curl or wget to test the upload endpoint, for example: curl -X POST -F "[email protected]" http://yourserver/common/jsp/upload2.jsp -v to see if file uploads are accepted without restriction. [2]
What immediate steps should I take to mitigate this vulnerability?
No known mitigations or countermeasures have been published by the vendor. Immediate steps include restricting access to the /common/jsp/upload2.jsp endpoint, for example by firewall rules or web server configuration to limit access only to trusted users or IPs. Consider disabling or removing the vulnerable upload functionality if possible. Monitoring and blocking suspicious upload attempts is recommended. Ultimately, replacing or upgrading the affected MetaCRM component or product to a non-vulnerable version is advised once available. [2]