Skip to content
Fencer Intel
critical 10.0

CVE-2019-16932 in the critical feed json

A blind SSRF vulnerability exists in the Visualizer plugin before 3.3.1 for WordPress via wp-json/visualizer/v1/upload-data.

published 7y ago modified 4mo ago also EUVD-2019-7425

cvss
10.0
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
39.0%
EPSS 39.0% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known, plus a Nuclei check

Summary

A blind SSRF vulnerability exists in the Visualizer plugin before 3.3.1 for WordPress via wp-json/visualizer/v1/upload-data.

Patch / fix

  • themeisle visualizer 3.3.1

Is CVE-2019-16932 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

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

Exploits and checks

  • Nuclei template Visualizer <3.3.1 - Blind Server-Side Request Forgery nuclei detection template
  • nathandavison.com https://nathandavison.com/blog/wordpress-visualizer-plugin-xss-and-ssrf referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-918 Server-Side Request Forgery
Technology feeds

References

Sources

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.