Vulnerability in Brave CMS (CVE-2026-35182)
Summary
Vulnerability in Brave CMS (CVE-2026-35182). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.0.6 or later.
Original description
The description as published by the source.
Brave CMS is an open-source CMS. Prior to 2.0.6, this vulnerability is a missing authorization check found in the update role endpoint at routes/web.php. The POST route for /rights/update-role/{id} lacks the checkUserPermissions:assign-user-roles middleware. This allows any authenticated user to change account roles and promote themselves to Super Admin. This vulnerability is fixed in 2.0.6.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-35182 has been found in Brave CMS.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade Brave CMS to 2.0.6 or later.
If unsure, ask your IT team or search "Brave CMS CVE-2026-35182" on the vendor's site.
CVE-2026-35182 (Brave CMS) — CWE-862 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.0.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in Brave CMS.
Check the vendor advisory for the affected versions of Brave CMS.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 2.0.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Brave CMS を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Brave CMS to 2.0.6ステージング環境で 2.0.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit github.com