# CVE-2026-35047: Brave CMS has Unrestricted File Upload in BraveCMS via CKEditor Endpoint

> Attackers can upload arbitrary executable files via the CKEditor endpoint in Brave CMS, leading to remote code execution and full system compromise.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-9rcc-w59j-965v

## What is CVE-2026-35047?

CVE-2026-35047 is a critical vulnerability in Ajax30 BraveCMS-2.0, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-35047?

It affects 1 product.


Products: Ajax30 Bravecms.

## How do I fix CVE-2026-35047?

No fix has been published for CVE-2026-35047 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-35047 being exploited?

There is no known exploitation of CVE-2026-35047 in the wild and no public exploit code.

## Other vulnerabilities in Ajax30 BraveCMS-2.0

- [CVE-2026-35164](https://insights.sbomify.com/CVE-2026-35164/): Brave CMS Sffected by Unrestricted File Upload via CKEditor Endpoint (high 8.8)
- [CVE-2026-35182](https://insights.sbomify.com/CVE-2026-35182/): Missing Authorization Privilege Escalation (high 8.8)
- [CVE-2026-35183](https://insights.sbomify.com/CVE-2026-35183/): Brave CMS has an Insecure Direct Object Reference in Article Image Deletion (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35047 and fix it if it is affected.

What it is: CVE-2026-35047 is a critical vulnerability in Ajax30 BraveCMS-2.0, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-35047 in the wild and no public exploit code.

Affected product: Ajax30 BraveCMS-2.0. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35047/ (Markdown: https://insights.sbomify.com/CVE-2026-35047/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35047
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35047
- OSV: https://osv.dev/vulnerability/CVE-2026-35047

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35047/
Summaries are generated and may contain mistakes; the official description above is the record.