CVE-2026-27603
Received Received - Intake
Unauthorized Access in Chartbrew Filter Endpoint via Missing Auth Middleware

Publication date: 2026-03-06

Last updated on: 2026-03-10

Assigner: GitHub, Inc.

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 version 4.8.4, the chart filter endpoint POST /project/:project_id/chart/:chart_id/filter is missing both verifyToken and checkPermissions middleware, allowing unauthenticated users to access chart data from any team/project. This issue has been patched in version 4.8.4.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-06
Last Modified
2026-03-10
Generated
2026-05-06
AI Q&A
2026-03-06
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
depomo chartbrew to 4.8.4 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-27603 is a high-severity vulnerability in the Chartbrew web application affecting versions up to 4.0.0. The issue exists because the POST endpoint /project/:project_id/chart/:chart_id/filter lacks the necessary authentication and authorization middleware (verifyToken and checkPermissions). This omission allows unauthenticated users to access and retrieve filtered chart data, including sensitive project metadata and team branding information, from any project or team simply by knowing the chart ID.

The vulnerable endpoint does not verify JWT tokens or user permissions, unlike other chart-related endpoints. This means anyone can access sensitive data without logging in, and because chart IDs are integer-based and sequential, an attacker can enumerate all charts in the system to extract data.

The vulnerability is classified under CWE-306: Missing Authentication for Critical Function and was fixed in Chartbrew version 4.8.4 by adding the missing authentication and authorization checks.


How can this vulnerability impact me? :

This vulnerability can have significant impacts including unauthorized data exposure and privacy breaches. Because unauthenticated users can access chart data from any team or project, sensitive information such as project metadata and team branding can be leaked.

Attackers can exploit the lack of authentication to enumerate all charts by their sequential IDs and retrieve confidential data without any credentials, potentially leading to data leakage, loss of confidentiality, and reputational damage.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by attempting to access the vulnerable POST endpoint without authentication and observing if chart data is returned.'}, {'type': 'paragraph', 'content': 'Specifically, sending unauthenticated POST requests to the endpoint /project/:project_id/chart/:chart_id/filter and checking if filtered chart data, project metadata, or team branding information is accessible indicates the presence of the vulnerability.'}, {'type': 'paragraph', 'content': 'Since the vulnerability allows unauthenticated access, you can use tools like curl to test this behavior.'}, {'type': 'list_item', 'content': "curl -X POST https://your-chartbrew-instance/project/1/chart/1/filter -d '{}' -v"}, {'type': 'paragraph', 'content': 'If the response contains chart data without requiring authentication tokens, the system is vulnerable.'}, {'type': 'paragraph', 'content': 'Additionally, monitoring network traffic for unauthenticated POST requests to this endpoint can help detect exploitation attempts.'}] [1]


What immediate steps should I take to mitigate this vulnerability?

[{'type': 'paragraph', 'content': 'The immediate and recommended mitigation is to upgrade Chartbrew to version 4.8.4 or later, where this vulnerability has been patched.'}, {'type': 'paragraph', 'content': 'The patch adds the missing verifyToken and checkPermissions("readOwn") middleware to the vulnerable POST /project/:project_id/chart/:chart_id/filter endpoint, enforcing proper authentication and authorization.'}, {'type': 'paragraph', 'content': 'If upgrading immediately is not possible, consider implementing temporary access controls such as network-level restrictions or API gateway rules to block unauthenticated access to the vulnerable endpoint.'}, {'type': 'paragraph', 'content': 'Also, review logs for any suspicious unauthenticated access to the endpoint and rotate any sensitive data that may have been exposed.'}] [1, 2]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart