dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-40603

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. In version 4.9.0, Chartbrew exposes a legacy dashboard route that returns a project's report data to any authenticated member of the same team, even when that user does not have access to the specific project. The route bypasses project-level authorization and returns the raw project object. As a result, a low-privileged same-team user can read another project's dashboard data and recover the project's stored report password from the response. This issue has been patched in version 5.0.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Chartbrew 4.9.0 contains a legacy dashboard route that bypasses project-level authorization, allowing any authenticated team member to access another project's report data and recover stored report passwords from the raw project object response.

MitigationUpgrade Chartbrew to version 5.0.0 which patches the authorization bypass. If immediate upgrade is not possible, restrict legacy route access at the API gateway or web server level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Chartbrew installation version
    Locate the Chartbrew instance and check its version (typically found in package.json, a version file, or the application's about/ status page). Compare the installed version to the affected range: version 4.9.0
    Affected if The installed version is exactly 4.9.0 or falls within the 4.x range prior to the patched version 5.0.0
  2. Confirm legacy dashboard route is accessible
    Attempt to access the legacy dashboard route endpoint (typically /dash/legacy or similar path referencing legacy dashboard functionality). This can be tested via browser navigation or by inspecting the application's route definitions in the source code if accessible.
    Affected if The legacy dashboard route responds successfully and returns project data without proper authorization checks
  3. Verify project-level authorization is enforced
    As an authenticated team member belonging to Project A, attempt to access or query data from Project B through the API. Inspect whether the application correctly denies access to projects outside the user's authorized scope.
    Affected if Authenticated users can retrieve data or report passwords from projects they are not members of, indicating the authorization bypass is present
  4. Check raw project object response for sensitive data exposure
    Make an authenticated API request to the legacy route and examine the response payload. Look for any password fields, credentials, or sensitive data embedded in the raw project object that should not be exposed to the requesting user.
    Affected if The API response includes stored report passwords or other sensitive credentials in plaintext within the project object

A user is affected if running Chartbrew 4.9.0 (or any pre-5.0.0 version) with the legacy dashboard route enabled, and an authenticated user can access data or credentials from projects they are not authorized to view.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Chartbrew to version 5.0.0 which patches the authorization bypass. If immediate upgrade is not possible, restrict legacy route access at the API gateway or web server level.

Recommended fix High confidence

5.0.0

  1. Identify the currently running Chartbrew version using the application's admin interface or deployment configuration
  2. Backup the existing Chartbrew database and configuration files
  3. Upgrade Chartbrew to version 5.0.0 or later by following the official upgrade documentation at https://chartbrew.com
  4. After upgrading, verify that the legacy dashboard route no longer exposes project data to unauthorized team members
  5. Confirm that users can only access project data for projects they have explicit permission to view
  6. Test with a low-privileged team member account to ensure the authorization bypass is resolved
Caveat Review the Chartbrew 5.0.0 release notes for any breaking changes or migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40603 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40603 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data