VulnerabilityPublished 12 Mar 2026

CVE-2026-3966: 648540858 wvp-GB28181-pro · Server-Side Request Forgery

Affects 648540858 wvp-GB28181-proSource CVE Database V5

Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
648540858wvp-GB28181-pro	Affected =2.7.4-20260107	Fixed in–
GitHub648540858/wvp-GB28181-pro`pkg:github/648540858/wvp-GB28181-pro`Other threats	Affected =2.7.4-20260107	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of an official patch, organizations should implement several specific mitigations to reduce risk. First, restrict network access to the wvp-GB28181-pro server, limiting exposure to trusted IP addresses and minimizing public accessibility. Employ network segmentation and firewall rules to prevent the server from initiating requests to sensitive internal services or metadata endpoints. Implement strict input validation and sanitization at the application or proxy level to detect and block malicious MediaServer.streamIp parameter values. Use web application firewalls (WAFs) with custom rules to identify and block SSRF attack patterns targeting this parameter. Monitor logs for unusual outbound requests originating from the server, which may indicate exploitation attempts. If feasible, deploy runtime application self-protection (RASP) solutions to detect and prevent SSRF behavior dynamically. Organizations should also engage with the vendor for updates and consider temporary compensating controls such as disabling or restricting the vulnerable functionality until a patch is available. Finally, conduct internal security assessments to identify and secure any internal services that could be targeted via SSRF.

Description

CVE-2026-3966 is a server-side request forgery (SSRF) vulnerability in the wvp-GB28181-pro product version up to 2.7.4-20260107. The flaw exists in the getDownloadFilePath function within the IP Address Handler component, specifically in the handling of the MediaServer.streamIp argument. An attacker can remotely manipulate this argument to cause the server to make unauthorized requests to internal or external systems. The vulnerability requires no user interaction and no authentication, increasing its risk. Although the vendor was notified, no patch or response has been provided yet. The CVSS 4.0 score is 5.

Impact

The SSRF vulnerability in wvp-GB28181-pro can have significant impacts on organizations using this software, especially those deploying it in sensitive or critical environments. Attackers exploiting this flaw can make the vulnerable server send crafted requests to internal systems that are otherwise inaccessible externally, potentially exposing internal services, metadata endpoints, or administrative interfaces. This can lead to unauthorized information disclosure, including sensitive configuration or credential data. Additionally, SSRF can be leveraged as a pivot point for further attacks such as remote code execution, lateral movement, or network reconnaissance. Since the vulnerability requires no authentication and no user interaction, it can be exploited remotely by unauthenticated attackers, increasing the attack surface. The lack of vendor response and patch availability further elevates the risk, as organizations remain exposed. The medium CVSS score reflects moderate impact, but the actual damage depends on the internal network architecture and the sensitivity of accessible resources. Overall, this vulnerability poses a moderate to high risk to confidentiality and integrity within affected environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Mar 2026, 02:33 UTC

Technical details

References

Community reviews

Related threats