Chartbrew: Unauthenticated Brute Force of Password-Protected Dashboards Due to Missing Rate Limit and Plaintext Password Storage
Affects Chartbrew instances with at least one public password-protected dashboard, in versions before 5.2.3. Fixed in 5.2.3.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.2.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.2.3.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Chartbrew, an open-source web app that builds charts from databases and APIs, has a flaw in its password-protected public dashboards: passwords are stored in plaintext, accepted via URL query parameters, and not effectively rate-limited. A remote attacker without logging in can repeatedly guess passwords to access the protected dashboard's chart data, or obtain passwords from server or proxy logs.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 5.2.3.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- chartbrew chartbrew
fixed in 5.2.3
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-68933
Is CVE-2026-68933 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The login endpoint for password-protected public dashboards does not limit repeated guesses, so an unauthenticated visitor can try many passwords until one works. Dashboard passwords are also stored in plaintext, so they are exposed in the database as well.Source: github.com
Which versions are affected by CVE-2026-68933?
chartbrew: before 5.2.3.Source: cve.now feed data
Am I affected, and how do I check?
Versions of Chartbrew before 5.2.3 are affected, but only when the instance has at least one public dashboard protected by a password. To check, look at the Chartbrew version you run and whether any public dashboard has a password set.Source: github.com
How do I fix CVE-2026-68933?
Upgrade Chartbrew to version 5.2.3 or later, which is the listed fixed version.Source: github.com