dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-13468

HIGH · 7.5 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Visualizer WordPress plugin (versions up to 4.0.3) registers a custom REST endpoint at /wp-json/visualizer/v1/action/{chart}/{type}/ that fails to perform proper capability checks, allowing unauthenticated attackers to export any chart data (including drafts, private, and trashed charts) as CSV, Excel, or HTML. This bypasses the protection that the standard WordPress REST API correctly enforces for the visualizer custom post type.

MitigationUpdate the Visualizer plugin to version 4.0.4 or later. Until updated, consider disabling the plugin or blocking unauthenticated access to the /wp-json/visualizer/ endpoints via web server configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Visualizer plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Visualizer' in the list, or check the file /wp-content/plugins/visualizer/ exists
    Affected if The Visualizer plugin is present in the WordPress installation
  2. Check installed Visualizer version
    In WordPress admin > Plugins > Installed Plugins, find Visualizer and note the version number displayed, or read version from /wp-content/plugins/visualizer/readme.txt
    Affected if Version is 4.0.3 or lower (any version up to and including 4.0.3)
  3. Test unauthenticated access to the vulnerable REST endpoint
    Send a GET request to /wp-json/visualizer/v1/action/1/csv/ (or any chart ID) without providing any authentication credentials (no cookies, no API keys)
    Affected if The endpoint returns HTTP 200 with exportable data (CSV/Excel/HTML content) without requiring login
  4. Verify chart data sensitivity
    In WordPress admin > Visualizer > Library, check if any charts exist with status Draft, Private, or Trash, or contain sensitive information
    Affected if Any charts exist in the WordPress visualizer library that could be exported without authentication

You are affected if the Visualizer plugin version is 4.0.3 or lower AND the /wp-json/visualizer/ REST endpoint is accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Visualizer plugin to version 4.0.4 or later. Until updated, consider disabling the plugin or blocking unauthenticated access to the /wp-json/visualizer/ endpoints via web server configuration.

Recommended fix Moderate confidence

Version 4.0.4 or later (check WordPress plugin repository for latest stable release)

  1. Check the WordPress plugin repository for Visualizer – Tables & Charts Manager with Built-in AI Generator to identify if version 4.0.4 or later has been released with a security fix
  2. If a fixed version is available, update the plugin to that version through the WordPress admin dashboard (Plugins > Add New > Upload or Updates)
  3. After updating, verify the /wp-json/visualizer/v1/action/{chart}/{type}/ endpoint no longer responds to unauthenticated requests
  4. Confirm that chart data is only accessible to authenticated users with appropriate capabilities

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13468 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13468 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data