CVE-2025-15098
Server-Side Request Forgery in YunaiV yudao-cloud BPM Component
Publication date: 2025-12-26
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 |
|---|---|---|
| yunai | yuandao_cloud | 2025.11 |
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-15098 is a server-side request forgery (SSRF) vulnerability in YunaiV yudao-cloud up to version 2025.11, specifically in the Business Process Management component's functions BpmHttpCallbackTrigger and BpmSyncHttpRequestTrigger. The vulnerability allows an attacker to manipulate the url, header, or body arguments to make the server send unauthorized HTTP requests to arbitrary destinations. This can be exploited remotely without authentication, and a public proof-of-concept exploit is available. [2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to make the server perform unauthorized requests to internal or external systems, potentially accessing sensitive information, interacting with internal network resources, or disrupting system availability. It compromises the confidentiality, integrity, and availability of the affected system. Since no authentication is required and public exploits exist, the risk of exploitation is significant. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this SSRF vulnerability involves monitoring and analyzing HTTP requests to the vulnerable BPM HTTP trigger functions (BpmHttpCallbackTrigger and BpmSyncHttpRequestTrigger) for unusual or unauthorized manipulation of url, header, or body parameters. Since the exploit is publicly available, you can use proof-of-concept scripts from the GitHub repository to test your system. Network monitoring tools can be used to detect unexpected outbound requests originating from the server. Specific commands are not provided in the resources, but using tools like curl or custom scripts to send crafted requests to these BPM endpoints can help detect the vulnerability. [1, 2, 3]
What immediate steps should I take to mitigate this vulnerability?
There are no known patches or vendor-provided mitigations for this vulnerability as the vendor did not respond. Immediate mitigation steps include considering replacing the affected product with an alternative, restricting network egress from the affected server to prevent unauthorized outbound requests, and limiting access to the BPM HTTP trigger functions to trusted users only. Monitoring and blocking suspicious requests targeting the vulnerable functions can also help reduce risk. [2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not contain information regarding the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.