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

CVE-2026-15189

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-09
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 6 weeks old

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 security vulnerability has been detected in aerostackdev aerostack-mcp up to 6315dfde7df0a15aaf743f88d91347115e09ba23. Affected by this issue is the function upload_media of the component mcp-whatsapp. Such manipulation of the argument media_url leads to server-side request forgery. The attack may be launched remotely. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The project was informed of the problem early through an issue report but has not responded yet.

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 · moderate confidence

Server-side request forgery (SSRF) vulnerability in the upload_media function of the mcp-whatsapp component allows remote attackers to control the media_url parameter and make the server request arbitrary URLs, potentially accessing internal services or bypassing network restrictions.

MitigationImplement strict URL validation with an allowlist of permitted domains/schemes for the media_url parameter, and restrict outbound network connections from the server to trusted endpoints only.

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. Confirm mcp-whatsapp installation
    Check for mcp-whatsapp in your installed packages or dependencies (e.g., pip list, npm list, or your package manager). Look for any package named mcp-whatsapp or related WhatsApp MCP components.
    Affected if mcp-whatsapp is installed and the upload_media function is exposed.
  2. Identify the upload_media function location
    Locate the upload_media function in the mcp-whatsapp codebase. Search for the function definition and identify the file path and endpoint that handles media uploads.
    Affected if The upload_media function exists in your environment and is accessible via an API or service.
  3. Verify media_url parameter handling
    Inspect the upload_media function code to see how the media_url parameter is processed. Check if the parameter is used directly in a request without validation, or if there is any URL validation in place.
    Affected if The media_url parameter is used directly in an HTTP request without strict allowlist validation.
  4. Check for input validation on media_url
    Review the code for any URL validation, allowlisting, or sanitization logic applied to the media_url parameter before the request is made. Look for functions that validate schemes, domains, or URL patterns.
    Affected if No validation or only weak validation exists on media_url, allowing arbitrary URLs.
  5. Assess network exposure of the upload endpoint
    Determine if the upload_media endpoint is exposed to untrusted network sources. Check API gateway, firewall rules, or authentication configuration for this endpoint.
    Affected if The endpoint is accessible to remote attackers without authentication or network restrictions.

Your environment is affected if mcp-whatsapp with the vulnerable upload_media function is installed, the media_url parameter accepts user-controlled input without strict allowlist validation, and the endpoint is accessible to untrusted callers.

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 URL validation with an allowlist of permitted domains/schemes for the media_url parameter, and restrict outbound network connections from the server to trusted endpoints only.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15189 — 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-2026-15189 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