External risk intelligence

Chartbrew SQL Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-54349

Chartbrew is designed to create charts and dashboards, which are frequently shared publicly or embedded in external-facing web applications. The vulnerability is reachable via unauthenticated crafted URL filter values sent to these public or embedded charts, making the attack surface commonly internet-facing.

SQL Injection

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security vulnerability in Chartbrew, an open-source web application for creating charts from data, could allow unauthorized access to sensitive information. The issue involves how the application processes data inputs, potentially enabling attackers to read, modify, or delete data if certain dashboard features are publicly exposed.

  • Unsafe data handling in Chartbrew.
  • Impacts public dashboards with SQL queries.
  • Confirm relevance and verify database exposure.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by sending specially crafted filter values in a URL to a public or embedded Chartbrew dashboard. This targets the application's handling of variables within SQL queries, particularly when used with MySQL or MariaDB databases. If successful, the attacker can execute arbitrary SQL commands against the database.

  • Publicly accessible or embedded chart exposure.
  • Crafted URL filter values sent to a chart.
  • Read, modify, or delete database data.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated user to manipulate SQL queries when public or embedded Chartbrew dashboards use URL-controlled variables. When supported by the advisory's context, this manipulation could lead to unauthorized data access, modification, or deletion.

  • Data in connected databases at risk.
  • Via crafted URL filter values.
  • Unauthorized data access or modification.

Operational Fix

Recommended remediation, mitigation, and detection steps

The application owner or platform team is likely responsible for Chartbrew instances. The first practical move is to identify all deployed Chartbrew instances, confirm if they expose public or embedded dashboards, and assess their business criticality and reachability. Based on this risk assessment, a plan for remediation, which may involve coordinating with the Chartbrew vendor for updates or implementing temporary risk reduction measures, can be developed.

  • Identify and locate all Chartbrew instances.
  • Verify public/embedded dashboards and data exposure.
  • Plan remediation based on risk and vendor guidance.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Chartbrew?

Chartbrew is an open-source tool that lets users connect their databases or APIs to a web interface to generate real-time charts and dashboards. Organizations use it to visualize business data, often by embedding these interactive charts directly into their own websites or sharing them via public links.

What does CWE-89 mean for CVE-2026-54349?

CVE-2026-54349 is classified as CWE-89, or Improper Neutralization of Special Elements used in an SQL Command, commonly known as SQL Injection. This happens when the application fails to properly clean user-provided inputs, allowing those inputs to change the structure of a database query and execute unauthorized commands.

How can an attacker trigger this vulnerability?

An attacker triggers this by sending malicious filter values through a URL to a dashboard that allows variable substitution in its SQL queries. Note that this only occurs on dashboards with URL-controlled variables; dashboards that do not use these variable inputs or are not publicly/externally accessible are not reachable through this specific path.

Do I need to worry if my dashboards are internal?

According to Halo Surface Signal, this vulnerability is particularly relevant because Chartbrew is frequently used for public or embedded charts, making the attack surface commonly internet-facing. If your dashboards are truly internal and restricted to authorized users, the risk is reduced; however, any instance exposing charts via public URLs should be prioritized.

When should I update my Chartbrew instance?

You should plan to update immediately. Start by auditing your environment to locate all Chartbrew deployments and identify which ones host public or embedded dashboards. Once mapped, upgrade to version 5.2.1, which corrects the unsafe variable handling and input sanitization flaws identified in the advisory.

References