External risk intelligence

Brave CMS Unrestricted File Upload Leads to Remote Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-35047

Brave CMS is a content management system. CMS platforms are typically deployed as internet-facing web applications to serve content to public users. Because the vulnerability exists within an endpoint accessible through the web application's interface, it is commonly exposed to the internet in standard deployments.

Unrestricted File Upload

Ajax30 Bravecms

2.0.0 to before 2.0.6

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability exists in Brave CMS that allows unauthorized file uploads, potentially leading to remote code execution and system compromise. This impacts all users running affected versions of the software.

  • Arbitrary file uploads can lead to server compromise.
  • This affects web content management systems.
  • Confirm relevance and exposure to Brave CMS.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by accessing the Brave CMS CKEditor endpoint to upload malicious files, such as executable scripts, to the server. This could lead to the execution of arbitrary code, potentially giving the attacker full control over the system, allowing them to steal data or disrupt services.

  • No authentication or user interaction required.
  • Upload arbitrary files via CKEditor endpoint.
  • Remote code execution and system compromise.

Live Threat

Current exploitation, exposure, and threat context

An unrestricted file upload vulnerability in Brave CMS's CKEditor endpoint could allow attackers to upload and execute arbitrary files, including scripts, on the server. This could lead to the compromise of the entire system, unauthorized access to data, or interruption of services.

  • Server code execution
  • Arbitrary file uploads
  • Full system compromise

Operational Fix

Recommended remediation, mitigation, and detection steps

The ownership of this vulnerability likely falls to the teams managing the Brave CMS application and its underlying infrastructure, such as application owners, platform teams, or system administrators. The immediate first step is to identify all instances of Brave CMS within your environment, assess their exposure and business criticality, and then determine the appropriate remediation plan.

  • Application owners and platform teams.
  • Verify Brave CMS instances and exposure.
  • Plan and coordinate remediation efforts.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Brave CMS?

Brave CMS is an open-source content management system (CMS) built by Ajax30. Like other systems in this category, it is designed to help users create, manage, and publish digital content on websites. It frequently utilizes integrated tools, such as the CKEditor, to provide a rich-text editing experience for authors when drafting posts or pages.

What does CVE-2026-35047 mean for Brave CMS?

This vulnerability is classified as Unrestricted File Upload (CWE-434). It means the application fails to properly validate the types of files users can upload through the editor. An attacker can abuse this by uploading malicious executable scripts instead of expected media files, which allows them to run unauthorized commands on the underlying server.

How is this file upload vulnerability triggered?

An attacker triggers this by sending specially crafted requests directly to the CKEditor endpoint used by Brave CMS. The vulnerability does not require the attacker to have an existing user account or perform any specific interaction on the site. However, simply browsing the site or uploading legitimate images via the editor does not trigger the flaw; it requires the deliberate upload of a malicious script file.

Why is this CVE considered high risk?

Halo Surface Signal notes that because Brave CMS is a web application meant to serve public content, its administrative and editing endpoints are frequently exposed to the internet. Because this flaw allows for Remote Code Execution without requiring authentication, any Brave CMS instance reachable from the public web is highly accessible to attackers looking to compromise server integrity.

What steps should I take if I use Brave CMS?

Your first priority is to audit your environment to locate all running instances of Brave CMS. Check your current version against the 2.0.6 release, as this update contains the necessary fix to restrict file uploads. If you are on any version prior to 2.0.6, plan to upgrade immediately to close the security gap and prevent unauthorized script execution on your server.

References