CVE-2026-13468 json
Visualizer <= 4.0.3 - Missing Authorization to Unauthenticated Sensitive Information Disclosure via /visualizer/v1/action/{chart}/{type}/ REST Endpoint
published 4mo ago modified 4mo ago also EUVD-2026-40892
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
The Visualizer – Tables & Charts Manager with Built-in AI Generator plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.0.3. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to access and export the contents of any visualizer chart on the site — including charts in draft, private, pending, future, or trash status — as CSV, Excel, or HTML via the /wp-json/visualizer/v1/action/{chart}/{type}/ REST endpoint. This bypass is particularly impactful because the standard WordPress REST endpoint for the non-public 'visualizer' custom post type correctly enforces capability checks and returns HTTP 401 to unauthenticated callers, whereas this plugin-registered route circumvents that protection entirely.
Is CVE-2026-13468 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- themeisle Visualizer – Tables & Charts Manager with Built-in AI Generator
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/45dbcc5e-2746-4a55-a1d1-a7c67fa2950e?source=cve
- plugins.trac.wordpress.org /browser/visualizer/tags/4.0.3/classes/Visualizer/Module/Frontend.php#L155
- plugins.trac.wordpress.org /browser/visualizer/tags/4.0.3/classes/Visualizer/Module.php#L182
- plugins.trac.wordpress.org /browser/visualizer/tags/4.0.3/classes/Visualizer/Module/Frontend.php#L219
- plugins.trac.wordpress.org /browser/visualizer/tags/4.0.1/classes/Visualizer/Module/Frontend.php#L155
- plugins.trac.wordpress.org /browser/visualizer/tags/4.0.1/classes/Visualizer/Module.php#L182
- plugins.trac.wordpress.org /browser/visualizer/tags/4.0.1/classes/Visualizer/Module/Frontend.php#L219
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3591310%40visualizer&new=3591310%40visualizer&sfp_email=&sfph_m
Sources
- CVE List CVE-2026-13468
- NVD CVE-2026-13468
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.