The SD-WAN Orchestrator 3.3.2 prior to 3.3.2 P3 and 3.4.x prior to 3.4.4 does not apply correct input validation which allows for SQL-injec…

published 2020-11-24 5y ago modified 2026-06-17 4mo ago also EUVD-2020-25249

cvss: 6.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 22.4%; EPSS 22.4% chance of exploitation in 30 days, percentile 97%
public exploits: 0; none known

The SD-WAN Orchestrator 3.3.2 prior to 3.3.2 P3 and 3.4.x prior to 3.4.4 does not apply correct input validation which allows for SQL-injection. An authenticated SD-WAN Orchestrator user may exploit a vulnerable API call using specially crafted SQL queries which may lead to unauthorized data access.

Patch / fix

fixed in 1

vmware sd-wan_orchestrator 3.4.4

Is CVE-2020-3984 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

22.37% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	4.0	AV:N/AC:L/Au:S/C:P/I:N/A:N

Affected products

n/a VMware SD-WAN Orchestrator

Classification

Weakness

CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

vmware.com /security/advisories/VMSA-2020-0025.html
third-party-advisory

Sources

CVE List CVE-2020-3984
NVD CVE-2020-3984

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.