CVE-2026-14939

Visualizer: Tables and Charts Manager <= 4.0.5 - Authenticated (Contributor+) Server-Side Request Forgery

2026-07-27 00:00
creeper_kirby

Strategic Overview

Status
Patched in 4.0.6
Affected Version
<= 4.0.5
CVSS
6.4Medium
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2026-14939
View all Visualizer – Tables & Charts Manager with Built-in AI Generator vulnerabilities

At a glance

CVE-2026-14939 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the Visualizer WordPress plugin, affecting versions <= 4.0.5. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 4.0.6; sites on affected versions should update now. Disclosed July 2026, reported by creeper_kirby.

Vulnerability Overview

The Visualizer: Tables and Charts Manager plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 4.0.5. This is due to insufficient URL validation in the JSON source connect() function, which called wp_safe_remote_request() directly without resolving and validating all DNS-returned addresses against private/reserved IP ranges, allowing DNS rebinding and SSRF via user-supplied import URLs. This makes it possible for authenticated attackers, with contributor-level access and above, to make web requests to arbitrary locations originating from the web application, including requests to internal network resources.

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 interaction from a victim user.

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

Visualizer <= 4.0.5 carries this weakness at connect(), and reaching it takes an account at Contributor level or above. 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 4.0.6: builds <= 4.0.5 are affected, anything from 4.0.6 onward is not.

Remediation

Update to version 4.0.6, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Visualizer 4.0.6 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