Unrestricted File Upload in Brave CMS (CVE-2026-35047)
Summary
Vulnerability in Brave CMS (CVE-2026-35047). Risk of unauthorized operations or information disclosure. 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, an Unrestricted File Upload vulnerability in the CKEditor endpoint allows attackers to upload arbitrary files, including executable scripts. This may lead to Remote Code Execution (RCE) on the server, potentially resulting in full system compromise, data exfiltration, or service disruption. All users running affected versions of BraveCMS are impacted. This vulnerability is fixed in 2.0.6.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-35047 has been found in Brave CMS.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Brave CMS to 2.0.6 or later.
If unsure, ask your IT team or search "Brave CMS CVE-2026-35047" on the vendor's site.
CVE-2026-35047 (Brave CMS) — CWE-434
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-434) exists in Brave CMS.
Check the vendor advisory for the affected versions of Brave CMS.
Severity: ?. Risk of unauthorized operations or information disclosure.
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
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com