原始描述
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.3, the shared project permission check trusted a caller-controlled team_id and let the teamOwner/teamAdmin branch continue without confirming that the target project belonged to that team. The vulnerable surface is project routes and related authorization checks that accepted user-controlled project identifiers. An authenticated user who is an owner or admin of their own team submits a victim project id together with the attacker's own team_id in the request body; default self-signup grants the required role on the user's own team. Authorization is evaluated against the attacker-selected team instead of the target project's team, and the update path mass-assigns the request body without a project field allow-list. The attacker needs a valid Chartbrew account, an owner or admin role on their own team, and a victim project identifier; requests without the body team_id trick are rejected. The attacker can re-parent the victim project into their own team, gain full read and write access, expose it publicly, remove password protection, and cause the victim to lose it; the shared delete route also permits cross-tenant deletion. This issue is fixed in version 5.2.3.
受影响的软件
- Chartbrew * 仓库或软件包匹配
详情
- 发布日期
- 2026-11-07
- 最后修改
- 2026-11-09
- CVSS 向量
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H- CWE
- CWE-639
- EPSS(30 天内被利用概率)
- 0.37% (百分位 31)
参考资料
本产品使用 NVD API 的数据,但未获得 NVD 的认可或认证。CVE® 是 The MITRE Corporation 的注册商标;CVE 记录依据 CVE Program 使用条款使用。