CVE-2026-86782

Visualizer – Tables & Charts Manager with Built-in AI Generator 4.0.0 - 4.0.5 - Authenticated (Contributor+) Insecure Direct Object Reference

2026-09-11 00:00
Artus KG

Strategic Overview

Status
Patched in 4.0.6
Affected Plugin
Visualizer – Tables & Charts Manager with Built-in AI Generator
Affected Version
4.0.0 – 4.0.5
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-86782
View all Visualizer – Tables & Charts Manager with Built-in AI Generator vulnerabilities

At a glance

CVE-2026-86782 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Visualizer WordPress plugin, affecting versions 4.0.0 – 4.0.5. It carries a CVSS score of 4.3 (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 September 2026, reported by Artus KG.

Vulnerability Overview

The Visualizer – Tables & Charts Manager with Built-in AI Generator plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions 4.0.0 through 4.0.5. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to perform an unauthorized action.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Visualizer 4.0.0 – 4.0.5 takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Visualizer the fix is 4.0.6: builds 4.0.0 – 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?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Visualizer 4.0.6 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-86782https://www.wordfence.com/threat-intel/vulnerabilities/id/1d211a77-82fe-4835-ac06-acec9e06864ahttps://nvd.nist.gov/vuln/detail/CVE-2026-86782

Related records

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