CVE-2019-16932

Visualizer: Tables and Charts Manager for WordPress <= 3.3.0 - Server-Side Request Forgery

2019-09-28 00:00
Nathan Davison

Strategic Overview

Status
Patched in 3.3.1
Affected Version
<= 3.3.0
CVSS
9.3Critical
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2019-16932
View all Visualizer – Tables & Charts Manager with Built-in AI Generator vulnerabilities

At a glance

CVE-2019-16932 is a critical-severity Server-Side Request Forgery (SSRF) vulnerability in the Visualizer WordPress plugin, affecting versions <= 3.3.0. It carries a CVSS score of 9.3 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 3.3.1; sites on affected versions should update now. Disclosed September 2019, reported by Nathan Davison.

Vulnerability Overview

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

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity.

CWE-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in Visualizer <= 3.3.0 takes a caller who can reach the endpoint. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Visualizer the fix is 3.3.1: builds <= 3.3.0 are affected, anything from 3.3.1 onward is not.

Remediation

Update to version 3.3.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Visualizer: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Visualizer 3.3.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C