dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-15098

MEDIUM · 6.3 CVSS v3.1 Published 2025-12-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in yudao-cloud's Business Process Management component. The BpmHttpCallbackTrigger and BpmSyncHttpRequestTrigger functions accept user-controllable url, header, and body parameters without proper validation, allowing remote attackers to induce the server to make requests to arbitrary URLs including internal infrastructure.

MitigationImplement strict allowlist-based URL validation for the callback trigger functions, restrict network access from the application server to internal resources, and consider disabling the HTTP callback functionality until an official patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if yudao-cloud is deployed
    Search for yudao-cloud application files, process list, or check for yudao/yudao-cloud identifiers in your environment
    Affected if yudao-cloud is present in the environment
  2. Locate the BPM component
    Search for bpm-related Java packages or classes, specifically looking for BpmHttpCallbackTrigger and BpmSyncHttpCallbackTrigger in the application codebase or deployment artifacts
    Affected if BpmHttpCallbackTrigger or BpmSyncHttpCallbackTrigger classes exist in the deployment
  3. Determine the yudao-cloud version
    Check application metadata (pom.xml, build.gradle, version files) or the about/version endpoint if exposed
    Affected if version is unknown or falls within recent releases containing the BPM HTTP callback feature
  4. Verify BPM HTTP callback endpoint is accessible
    Check application routing/configuration for BPM-related HTTP endpoints, looking for paths related to httpCallback or syncCallback in BPM controllers
    Affected if BPM HTTP callback endpoints are exposed and accessible to users
  5. Inspect BPM callback configuration
    Review BPM module configuration files or database tables for httpCallback-related settings that accept user-supplied URL parameters
    Affected if configuration allows user-controllable url, header, or body parameters for BPM HTTP callbacks

The environment is affected if yudao-cloud with the BPM component is deployed and the BpmHttpCallbackTrigger or BpmSyncHttpCallbackTrigger functionality is enabled with user-accessible endpoints accepting url parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based URL validation for the callback trigger functions, restrict network access from the application server to internal resources, and consider disabling the HTTP callback functionality until an official patch is released.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15098 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15098 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data