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

CVE-2026-3966

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-12
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 detected in 648540858 wvp-GB28181-pro up to 2.7.4-20260107. Affected by this vulnerability is the function getDownloadFilePath of the file /src/main/java/com/genersoft/iot/vmp/media/abl/ABLMediaNodeServerService.java of the component IP Address Handler. The manipulation of the argument MediaServer.streamIp results in server-side request forgery. The attack may be launched remotely. The exploit is now public 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

This is a Server-Side Request Forgery (SSRF) vulnerability in the wvp-GB28181-pro video management platform. The getDownloadFilePath function in ABLMediaNodeServerService.java accepts the MediaServer.streamIp parameter without proper validation, allowing remote attackers to induce the server to make arbitrary HTTP requests to internal or external resources.

MitigationImplement strict allow-list validation for the MediaServer.streamIp parameter to ensure only permitted IP addresses or hostnames can be used, preventing the server from making requests to internal infrastructure or arbitrary external URLs.

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 wvp-GB28181-pro is installed
    Search for the application installation directory or running process. Look for files named ABLMediaNodeServerService.java or the compiled class, or check for the wvp-GB28181-pro service running on common ports (such as 8080, 18080).
    Affected if The application wvp-GB28181-pro is found running or installed on the system
  2. Determine the installed version
    Check the application's version information in the installation folder, pom.xml, or the running service banner. Common locations: /opt/wvp, /home/wvp, or the war/jar file name.
    Affected if The version cannot be determined or falls within an affected version range (compare your installed version to any official vulnerability advisory)
  3. Verify the ABLMediaNodeServerService component is exposed
    Identify if the ABLMediaNodeServerService.java component is accessible. Check the application's API endpoints or web service paths. Look for URLs containing 'ABLMediaNodeServerService' or related media server endpoints.
    Affected if The ABLMediaNodeServerService endpoint is accessible via HTTP/HTTPS
  4. Check if MediaServer.streamIp parameter is controllable
    Examine the application's API parameters or configuration to determine if the MediaServer.streamIp parameter can be supplied via user input (query parameters, request body, or configuration). Review the getDownloadFilePath function handling.
    Affected if The streamIp parameter accepts user-controlled input without validation

You are affected if wvp-GB28181-pro is running and the ABLMediaNodeServerService endpoint is accessible with the MediaServer.streamIp parameter user-controllable.

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 allow-list validation for the MediaServer.streamIp parameter to ensure only permitted IP addresses or hostnames can be used, preventing the server from making requests to internal infrastructure or arbitrary external URLs.

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-3966 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-3966 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