CVE-2025-10391
BaseFortify
Publication date: 2025-09-14
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 |
|---|---|---|
| crmeb | crmeb | to 5.6.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-10391 is a Server-Side Request Forgery (SSRF) vulnerability in CRMEB up to version 5.6.1. It occurs in the function testOutUrl of the file app/services/out/OutAccountServices.php, where the push_token_url parameter is not properly validated before being used in HTTP requests. This allows an authenticated administrator to manipulate the URL and cause the server to send unauthorized HTTP or HTTPS requests to arbitrary internal or external network resources. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow an attacker with administrator access to make the server perform unauthorized requests to arbitrary URLs, potentially leading to unauthorized access to internal network resources, information disclosure, and compromise of confidentiality, integrity, and availability of the system. The exploit is remotely accessible and publicly available, increasing the risk of exploitation. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by searching for the presence of the vulnerable endpoint `app/services/out/OutAccountServices.php` on your system or network. You can use network scanning or web application scanning tools to identify this path. Additionally, Google dorking with the query `inurl:app/services/out/OutAccountServices.php` can help identify exposed vulnerable targets. To detect exploitation attempts, monitor server logs for unusual or unauthorized HTTP requests originating from the server, especially those involving the `push_token_url` parameter. Specific commands might include using curl or wget to test the endpoint manually, for example: `curl -v https://yourserver/app/services/out/OutAccountServices.php` and checking logs for suspicious activity. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable endpoint to trusted administrators only, implementing network-level controls to prevent the server from making unauthorized outbound HTTP/HTTPS requests, and monitoring for exploitation attempts. Since no official patch or mitigation has been provided by the vendor, consider disabling or replacing the affected component or application version. Applying strict input validation or filtering on the `push_token_url` parameter to prevent arbitrary URLs may also help reduce risk until a proper fix is available. [2]