CRMEB up to 5.6.1 OutAccountServices.php testOutUrl push_token_url server-side request forgery
Summary
A vulnerability was found in CRMEB up to 5.6.1. It has been declared as critical. This affects the function testOutUrl of the file app/services/out/OutAccountServices.php. The manipulation of the argument push_token_url results in server-side request forgery.
This vulnerability is identified as CVE-2025-10391. The attack can be executed remotely. Additionally, an exploit exists.
The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability was found in CRMEB up to 5.6.1. It has been classified as critical. Affected is the function testOutUrl of the file app/services/out/OutAccountServices.php. The manipulation of the argument push_token_url with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is available at github.com. This vulnerability is traded as CVE-2025-10391. The exploitability is told to be easy. It is possible to launch the attack remotely. Technical details and a public exploit are known.
The exploit is shared for download at github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way. By approaching the search of inurl:app/services/out/OutAccountServices.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at CNNVD (CNNVD-202509-1866) and EUVD (EUVD-2025-29109). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 6.9
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔒
CNA Base Score: 6.3
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Google Hack: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
09/13/2025 Advisory disclosed09/13/2025 VulDB entry created
10/15/2025 VulDB entry last update
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2025-10391 (🔒)
GCVE (CVE): GCVE-0-2025-10391
GCVE (VulDB): GCVE-100-323826
EUVD: 🔒
CNNVD: CNNVD-202509-1866 - CRMEB 代码问题漏洞
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/13/2025 11:51Updated: 10/15/2025 08:32
Changes: 09/13/2025 11:51 (56), 09/14/2025 08:00 (30), 09/14/2025 09:55 (1), 09/15/2025 20:37 (6), 10/15/2025 08:32 (11)
Complete: 🔍
Submitter: Yu Bao
Cache ID: 216::103
Submit
Accepted
- Submit #644582: crmeb CRMEB-KY v5.6.1 SSRF (by Yu Bao)
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.