# CVE-2026-35183: Ajax30 Brave CMS IDOR in article image deletion

Source: https://junglewise.ai/threats/cve-2026-35183-ajax30-brave-cms-idor-in-article-image-deletion  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-06. Updated: 2026-07-24  
License: CC BY 4.0 with a link back

CVE-2026-35183 · Severity: high · CVSS 7.1 · Published 2026-04-06

Brave CMS is an open-source content management system used to build and manage websites. A security flaw in the article management feature allows any user with basic editing permissions to delete images belonging to other users' articles. This could lead to unauthorized data loss and disruption of website content by malicious or disgruntled users.

Technologies: [Ajax30 Bravecms](https://junglewise.ai/threats/technologies/bravecms). Vendors: [Ajax30](https://junglewise.ai/threats/vendors/ajax30).

## Quick answers

**Is CVE-2026-35183 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-35183 being exploited in the wild.

**How severe is CVE-2026-35183?** High severity, with a CVSS score of 7.1, published 6 April 2026.

**Which products and versions are affected?** Ajax30 BraveCMS-2.0 2.0.0 to 2.0.5.

**Is there a fix for CVE-2026-35183?** A patch was published on 2026-04-06: Fix released in version 2.0.6 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-35183 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-35183?** Check whether you run Ajax30 Bravecms or Ajax30 BraveCMS-2.0 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

An Insecure Direct Object Reference (IDOR) vulnerability exists in Brave CMS within the `deleteImage` method of `app/Http/Controllers/Dashboard/ArticleController.php`. The application processes image deletion requests via a URL endpoint that accepts a filename and article ID but fails to verify if the authenticated user owns the target article. An attacker with standard 'author' or 'editor' privileges can exploit this by sending a crafted POST request to `/dashboard/articles/delete-image/{id}/{filename}` to delete arbitrary images from the server's storage. The vulnerability is addressed in version 2.0.6 by implementing ownership checks and filename validation.

## Affected products

- Ajax30 BraveCMS-2.0 2.0.0 to 2.0.5

## Timeline

- 2026-04-01: advisory: GitHub security advisory published by vendor
- 2026-04-06: disclosed: CVE published to NVD
- 2026-04-06: patched: Fix released in version 2.0.6

## References

- [https://github.com/Ajax30/BraveCMS-2.0/security/advisories/GHSA-cpf3-fxwg-cwr3](https://github.com/Ajax30/BraveCMS-2.0/security/advisories/GHSA-cpf3-fxwg-cwr3)

## Related threats

- [Ajax30 Brave CMS privilege escalation in update role endpoint](https://junglewise.ai/threats/cve-2026-35182-ajax30-brave-cms-privilege-escalation-in-update-role-endpoint)
- [Brave CMS is an open-source CMS. Prior to 2.0.6, an unrestricted file upload vulnerability exists in the CKEditor…](https://junglewise.ai/threats/cve-2026-35164-brave-cms-is-an-open-source-cms-prior-to-2-0-6-an-unrestricted)
- [Brave CMS is an open-source CMS. Prior to 2.0.6, an Unrestricted File Upload vulnerability in the CKEditor endpoint…](https://junglewise.ai/threats/cve-2026-35047-brave-cms-is-an-open-source-cms-prior-to-2-0-6-an-unrestricted)