dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-40600

HIGH · 8.1 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 →
87/100
Remediation priority · High
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 allows authenticated users with access to one project to update or delete a SharePolicy record that belongs to a different project. The affected routes authorize the caller against the project in the URL path, but they never verify that policy_id belongs to that project. This permits cross-project modification of dashboard sharing rules, including visibility, password requirements, allowed parameters, and expiration settings. 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

This is an Insecure Direct Object Reference (IDOR) vulnerability in Chartbrew where authenticated users can modify SharePolicy records belonging to different projects. The application validates user access to the project in the URL path but fails to verify that the policy_id being modified actually belongs to that project, allowing cross-project modification of dashboard sharing rules.

MitigationUpgrade to Chartbrew version 5.0.0 or later which contains the security patch for this vulnerability.

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Confirm Chartbrew is installed
    Look for Chartbrew application files, typically installed via npm (node_modules/chartbrew) or Docker containers named 'chartbrew'. Check for the presence of the chartbrew application directory.
    Affected if Chartbrew is not present in the environment
  2. Determine installed Chartbrew version
    Check package.json in the Chartbrew installation directory for the version field, or run 'npm list chartbrew' if installed as a dependency. For Docker, inspect the image tag or label.
    Affected if Version is present and is before 5.0.0 (e.g., 4.x, 3.x, etc.)
  3. Verify sharing/policy feature is in use
    Examine the Chartbrew database for SharePolicy or sharing-related tables. Check if any projects have sharing enabled or if there are records in tables related to share_policies, project_sharing, or similar.
    Affected if Sharing policies exist and projects have sharing enabled
  4. Check for multiple projects with sharing enabled
    Query the database to identify projects that have share policies configured. Look for any share_policy records and their associated project_id values.
    Affected if Multiple projects exist with share policy records, allowing cross-project access attempts
  5. Test policy modification endpoint access control
    If authenticated access is possible, attempt to modify a SharePolicy from one project while accessing through a different project's URL path, observing whether the application accepts the cross-project request.
    Affected if The application allows modification of SharePolicy records belonging to a project different from the one in the URL path

The environment is affected if Chartbrew versions before 5.0.0 are running with the sharing/policy feature enabled and multiple projects exist with share policies configured.

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 to Chartbrew version 5.0.0 or later which contains the security patch for this vulnerability.

Recommended fix Moderate confidence

version 5.0.0

  1. 1. Back up your current Chartbrew installation and database
  2. 2. Check Chartbrew's official GitHub repository for the v5.0.0 release notes
  3. 3. Review the migration guide for upgrading from v4.x to v5.0.0
  4. 4. Execute the upgrade process according to the official documentation
  5. 5. Verify that the IDOR vulnerability is resolved by testing cross-project SharePolicy access attempts
Caveat Upgrading from v4.x to v5.0.0 may introduce breaking changes; review the changelog for API and configuration changes

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40600 — 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-40600 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