sales@hackhalt.com

Home / Threats / CVE-2026-86784

Visualizer - Security Vulnerability (CVE-2026-86784)

CVE-2026-86784

The Visualizer WordPress plugin before 4.0.8 does not sanitise and escape a chart's JSON data source configuration before outputting it back in the chart editor, allowing users with the Contributor role and above to store JavaScript that executes in the browser of any higher-privileged user, such as an administrator, who reviews the affected chart.

CVE-2026-86784

MEDIUM CVSS 6.8 Published 2026-09-16 Updated 2026-09-17
AI Risk Elevated (66/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
Affected Components 1
Reference Links 1
AI Risk Engine Elevated (66/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-09-16 CVE published and first recorded in the threat feed.
  2. 2026-09-17 Record updated with latest vulnerability metadata.
  3. 2026-09-20 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 22 hours ago

AI enriched 22 hours ago (2026-09-20 21:09 UTC)

Technical Summary

The Visualizer WordPress plugin before 4.0.8 does not sanitise and escape a chart's JSON data source configuration before outputting it back in the chart editor, allowing users with the Contributor role and above to store JavaScript that executes in the browser of any higher-privileged user, such as an administrator, who reviews the affected chart.

Potential Impact

Severity is MEDIUM (CVSS 6.8). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential.

Primary risk drivers: remote code execution potential

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 66/100 (Elevated, High) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Visualizer PLUGIN · visualizer Affected: < 4.0.8 Fixed in: 4.0.8

References

What to do about this

Patch on your next cycle Worth fixing, but not ahead of other work.

Fix it

Update Visualizer to 4.0.8 or later.

That is the complete fix. Everything below is what protects you in the meantime.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Visualizer, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Visualizer. Versions below 4.0.8 are vulnerable; that release and later are not. An attacker needs contributor or above, so open registration materially increases the risk.

How do I fix it?

Update Visualizer to version 4.0.8 or later. That is the complete fix. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Cross-Site Scripting (XSS) flaw. An attacker who exploits it can run script in a visitor's browser, stealing sessions or planting an administrator account.