# CVE-2026-19726: Visualizer < 4.0.7 - Contributor+ Cross-User Chart Configuration Disclosure

> Contributors can read full chart configurations, potentially exposing remote data source credentials, due to missing authorization checks.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-v7fh-395c-948j

## What is CVE-2026-19726?

CVE-2026-19726 is a medium-severity missing authorization vulnerability in Unknown Visualizer, published on 16 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Visualizer  WordPress plugin before 4.0.7 does not properly authorise access to the configuration of its charts, allowing users with the Contributor role and above to read the full configuration of any chart on the site, including charts the Visualizer  WordPress plugin before 4.0.7's own interface denies them, and to retrieve every chart's configuration in a single request. The disclosed configuration can include the credentials of a remote data source a chart reads from.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-19726?


## How do I fix CVE-2026-19726?

No fix has been published for CVE-2026-19726 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19726 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19726 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19726 and fix it if it is affected.

What it is: CVE-2026-19726 is a medium-severity missing authorization vulnerability in Unknown Visualizer, published on 16 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19726 exists.

Affected product: Unknown Visualizer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19726/ (Markdown: https://insights.sbomify.com/CVE-2026-19726/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19726
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19726
- OSV: https://osv.dev/vulnerability/CVE-2026-19726

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19726/
Summaries are generated and may contain mistakes; the official description above is the record.