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.
Published: 2026-11-06
Score: 9.8 Critical
EPSS: n/a
KEV: No
Impact: Data Compromise via SQL Injection
Action: Immediate Patch
AI Analysis

Impact

Chartbrew, an open‑source dashboard application, has a critical SQL injection flaw in its dashboard‑variable substitution logic. The vulnerability allows an unauthenticated attacker to inject arbitrary SQL through crafted URL filter values that are substituted into stored queries. This oversight, classified as CWE-89, lets a user read, modify or delete data accessible to the database account used by the application.

Affected Systems

All Chartbrew installations running a version earlier than 5.2.1 that expose public or embedded dashboards with URL‑controlled variables in a SQL query are vulnerable. The flaw applies to any database connector, and an additional back‑slash escape workaround can also be exploited when the target uses MySQL or MariaDB.

Risk and Exploitability

The flaw carries a CVSS score of 9.8, reflecting its high severity. Exploitation is possible over the public web interface without authentication, making it broadly exploitable. Because the EPSS score is not available, the precise current attack frequency is unclear, and the vulnerability is not listed in the CISA KEV catalog. The attacker can execute the injected SQL independently of the underlying database engine, and when targeting MySQL or MariaDB the back‑slash handling offers an alternative path for injection.

Generated by OpenCVE AI on November 6, 2026 at 22:27 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Chartbrew v5.2.1 or later, which removes the unsafe variable substitution and correctly escapes backslashes.
  • If upgrading is temporarily infeasible, disable public or embedded dashboard features or restrict their use to authenticated users only to prevent unauthenticated injection.
  • Review and sanitize any remaining URLs that accept user input for SQL variables, applying strict input validation and rejecting dangerous characters such as quotes, semicolons and back‑slashes.

Generated by OpenCVE AI on November 6, 2026 at 22:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 06 Nov 2026 23:00:00 +0000

Type Values Removed Values Added
First Time appeared Chartbrew
Chartbrew chartbrew
Vendors & Products Chartbrew
Chartbrew chartbrew

Fri, 06 Nov 2026 21:15:00 +0000

Type Values Removed Values Added
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.
Title Chartbrew SQL injection in dashboard filter substitution
Weaknesses CWE-89
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Subscriptions

Chartbrew Chartbrew
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-11-06T21:04:39.792Z

Reserved: 2026-06-12T19:23:22.317Z

Link: CVE-2026-54349

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2026-11-06T21:17:08.947

Modified: 2026-11-06T21:17:09.090

Link: CVE-2026-54349

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-06T22:45:11Z

Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')