CVE-2026-35047
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBrave 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn unrestricted file upload vulnerability exists in the CKEditor endpoint of Brave CMS versions prior to 2.0.6. Attackers can upload arbitrary files, including executable scripts, which can be triggered to achieve remote code execution on the server, leading to full system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.0.0, < 2.0.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Brave CMS is installedLook for CMS installation directories or check web server logs for 'bravecms' or 'Brave' references. Common paths include /admin, /cms, or application root directories.Affected if Brave CMS files are present on the server
-
Determine the installed Brave CMS versionCheck the version file in the CMS installation directory. Look for a version.php, version.json, or similar file that displays the current version number.Affected if The installed version is 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, or 2.0.5 (any version >= 2.0.0 but < 2.0.6)
-
Verify the CKEditor endpoint is exposedAttempt to access the CKEditor upload endpoint. Common paths include /ckeditor/fileupload, /ckeditor/uploader, or /includes/ckeditor/upload.aspx. Check if the endpoint returns a valid response.Affected if The CKEditor upload endpoint is accessible and accepts requests without authentication restrictions
A system is affected if Brave CMS versions 2.0.0 through 2.0.5 are installed and the CKEditor file upload endpoint is accessible without proper restrictions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.0.6
Upgrade to Brave CMS version 2.0.6 or later. As an interim measure, restrict network access to the CKEditor endpoint and implement file type validation at the web server level until the patch can be applied.
2.0.6
- 1. Back up your current BraveCMS installation and database before making any changes.
- 2. Navigate to your BraveCMS installation directory.
- 3. Use your preferred method to update to version 2.0.6 (e.g., composer update, git pull, or manual file replacement).
- 4. If using git, run: git pull origin main or fetch and checkout to the v2.0.6 tag.
- 5. Verify the update was successful by checking the admin interface shows version 2.0.6.
- 6. Test the CKEditor file upload functionality to confirm the vulnerability is patched and only allowed file types are accepted.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35047 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35047 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data