Chartbrew: Blind NoSQL injection via date variable in embedded chart
Chartbrew server 5.2.2 and earlier, with a MongoDB data connection and a public, shareable, or embedded chart that puts a date variable in a quoted literal. 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 tool for building charts from databases and APIs, is affected by a blind NoSQL injection flaw in public, shareable, or embedded MongoDB charts that use a date variable inside a quoted query placeholder. Remotely, without logging in, an attacker can craft a URL filter that lets them read any field in the queried collection, including secrets the chart does not display.
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, a date-typed MongoDB variable placed inside a quoted query placeholder was inserted as an unescaped string, unlike the safely escaped or coerced string, number, and Boolean branches. The vulnerable surface is mongoDB-backed public, shareable, or embedded charts processed by date-variable substitution. An unauthenticated user supplies a crafted URL filter to a public, shareable, or embedded MongoDB chart whose query places a date-typed variable in a quoted literal. The crafted date value breaks out of the quoted literal and changes query logic; the chart's returned row count becomes a Boolean oracle for character-by-character field extraction. The chart must be externally reachable and use the vulnerable date-in-quoted-placeholder branch. Extraction is read-only and limited to one queried collection per request, and it requires neither an account nor a known field value. The blind oracle can disclose any field in the queried collection, including secrets the chart does not display. This issue is fixed in version 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-85726
Is CVE-2026-85726 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?
A date-typed variable placed inside a quoted literal in a chart's MongoDB query allows NoSQL injection that works blind, meaning the results are inferred from the server's responses. An anonymous reader can use this to read any field in the collection the shared chart queries, including secrets the chart never displays.Source: github.com
Which versions are affected by CVE-2026-85726?
chartbrew: before 5.2.3.Source: cve.now feed data
Am I affected, and how do I check?
Chartbrew server version 5.2.2 or earlier, where a chart uses a MongoDB data connection and its query places a date-typed variable in a quoted literal. The chart must be public, shareable, or embedded, and the embed route needs no token. Check the installed server version and review chart queries that use date variables in quoted literals.Source: github.com
How do I fix CVE-2026-85726?
Upgrade the Chartbrew server to version 5.2.3 or later, which is the listed fixed version.Source: github.com