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

CVE-2026-6979

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-25
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 flaw has been found in devlikeapro WAHA up to 2026.3.4. This affects an unknown function of the file src/api/media.controller.ts of the component API Request Handler. This manipulation causes server-side request forgery. The attack can be initiated remotely. The exploit has been published and may be used. 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

A server-side request forgery (SSRF) vulnerability exists in the WAHA media.controller.ts API endpoint. An attacker can manipulate the API to cause the server to make arbitrary requests to internal or external resources, potentially accessing internal services, cloud metadata endpoints, or internal network resources.

MitigationImplement strict allowlist-based URL validation for the media endpoint, restrict server outbound network access via firewall rules, and apply network segmentation to limit exposure of internal services.

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 WAHA deployment
    Identify if WAHA (Web Abstract HTTP API for WhatsApp) is running in your environment by checking for WAHA processes, Docker containers, or services listening on typical WAHA ports (default: 3000).
    Affected if WAHA is running and the media.controller.ts endpoint is accessible
  2. Determine WAHA version
    Check the installed WAHA version by inspecting the Docker image tag, package.json version field, or running 'npm list waha' / 'docker images | grep waha' if applicable. Compare your version against any official release notes or changelogs for CVE-2026-6979.
    Affected if Your WAHA version is unpatched for the SSRF vulnerability in media.controller.ts
  3. Verify media API endpoint exposure
    Inspect your WAHA configuration files (typically waha.yaml, .env, or config.js) to confirm the media controller endpoint is enabled. Look for routes or settings related to 'media', 'controller', or API endpoints under '/api/media'.
    Affected if The media controller endpoint is enabled and routable in your WAHA instance
  4. Check for URL validation configuration
    Review WAHA configuration files and any proxy/web server configurations (nginx, caddy, etc.) for URL validation rules, allowlists, or input sanitization applied to the media endpoint. Look for patterns like url validation, whitelist, or allowed domains.
    Affected if No strict allowlist-based URL validation is configured for the media endpoint
  5. Assess network exposure
    Review firewall rules, security groups, or network policies to determine if your WAHA server can make outbound HTTP/HTTPS requests to internal network ranges (RFC1918 addresses) or cloud metadata endpoints (169.254.169.254).
    Affected if The WAHA server has unrestricted outbound network access and can reach internal resources

You are affected if WAHA is running with the media controller endpoint enabled and without strict URL validation, allowing an attacker to trigger arbitrary requests from your server to internal or external resources.

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 media endpoint, restrict server outbound network access via firewall rules, and apply network segmentation to limit exposure of internal services.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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