Chartbrew SQL injection in dashboard filter substitution
- Exploited
- No known exploitation
- Fix
- Fixed in 5.2.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.2.1.
- 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? →
- 27/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 tool for building charts from databases and APIs, is affected by an SQL injection flaw in how dashboard filter values are inserted into queries. A remote attacker without logging in can send crafted URL filter values to a public or embedded chart backed by a stored SQL query, and read, modify, or delete data available to the configured database account; the flaw requires the target to expose such a chart.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
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.1, SQL dashboard-variable substitution used attacker-controlled JavaScript replacement strings unsafely across SQL connectors and separately failed to escape backslashes for MySQL and MariaDB quoted contexts. The vulnerable surface is public and embedded dashboard/chart requests that call applyMysqlOrPostgresVariables. An unauthenticated user sends crafted URL filter values to a public or embedded chart backed by a stored SQL query. Replacement-string dollar sequences can alter SQL independently of the database engine, while MySQL and MariaDB backslash handling provides a second quoted-string escape path. The target must expose a public or embedded chart using URL-controlled variables in a SQL query; only the backslash branch is specific to MySQL and MariaDB. Injected SQL can read, modify, or delete data available to the configured database account. This issue is fixed in version 5.2.1.
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
- Severity9.8/10CVSS 9.8
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 5.2.1.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- chartbrew chartbrew
fixed in 5.2.1
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-54349
Is CVE-2026-54349 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?
Chartbrew fills a chart's stored SQL query with values taken from URL parameters, and the substitution does not escape them properly. A crafted URL parameter can therefore change the SQL that runs against the connected database, which can read, modify, or delete data depending on the database user's privileges.Source: github.com
Which versions are affected by CVE-2026-54349?
chartbrew: before 5.2.1.Source: cve.now feed data
Am I affected, and how do I check?
Chartbrew versions before 5.2.1 are in scope. The issue needs a chart that is public or embedded, since the share and embed routes skip authentication, and a stored query that uses dashboard variables filled from URL parameters. The backslash escape path applies only to MySQL or MariaDB connections, while the dollar-sequence replacement issue applies to all SQL connectors. To check, look at the Chartbrew version in use and whether the chart is shared or embedded and uses dashboard variables in its query.Source: github.com
How do I fix CVE-2026-54349?
Upgrade Chartbrew to 5.2.1 or later, which is the listed fixed version.Source: github.com