CVE-2026-68933 · Package
NO FIX YET · SEE WHAT TO DO
Chartbrew stores public dashboard passwords in plaintext and accepts them in URL query strings, and it does not effectively throttle password guesses. An unauthenticated attacker can brute-force a password-protected public dashboard or read the password from server or proxy logs, then see the protected chart data.
first public Sep 20, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Only deployments of Chartbrew before 5.2.3 that serve public dashboards with password protection enabled are exposed. Instances without public password-protected dashboards, or on 5.2.3 or later, are not affected. Access logs for those dashboards may already contain the password.
Not affected if fixed-version, no-dashboard-passwords, no-public-dashboards
Who cares chartbrew, dashboards, self-hosted
5.2.3.password query parameter.5.2.3 or later.Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.3, public dashboard passwords were stored in plaintext, accepted through a URL query parameter, and checked without effective attempt throttling. The vulnerable surface is public password-protected dashboard storage and validation routes. An unauthenticated attacker targets a public password-protected dashboard and repeatedly submits candidate passwords or obtains password-bearing server or proxy logs. Unlimited online guesses enable brute force, while cleartext storage and URL transport expose the secret in application storage and server or proxy access logs. The target must be a public dashboard with password protection enabled. Even failed attempts reveal chart count and configuration without the password; a recovered password grants access to the protected dashboard and its chart data. This vulnerability is fixed in 5.2.3.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.