CVE-2025-15098
Unknown Unknown - Not Provided
Server-Side Request Forgery in YunaiV yudao-cloud BPM Component

Publication date: 2025-12-26

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was determined in YunaiV yudao-cloud up to 2025.11. This affects the function BpmHttpCallbackTrigger/BpmSyncHttpRequestTrigger of the component Business Process Management. Executing manipulation of the argument url/header/body can lead to server-side request forgery. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-26
Last Modified
2026-04-29
Generated
2026-06-16
AI Q&A
2025-12-26
EPSS Evaluated
2026-06-15
NVD
CVE-2025-15098
EUVD
EUVD-2025-205414
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
yunai yuandao_cloud 2025.11
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Executive Summary

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]

Impact Analysis

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]

Detection Guidance

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]

Mitigation Strategies

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]

Compliance Impact

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.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-15098. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart