CVE-2026-35183: high-severity vulnerability in Ajax30 BraveCMS-2.0
Brave CMS has an Insecure Direct Object Reference in Article Image Deletion
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.1epss 0.2%
Brave CMS is an open-source CMS. Prior to 2.0.6, an Insecure Direct Object Reference (IDOR) vulnerability exists in the article image deletion feature. It is located in app/Http/Controllers/Dashboard/ArticleController.php within the deleteImage method. The endpoint accepts a filename from the URL but does not verify ownership. This allows an authenticated user with edit permissions to delete images attached to articles owned by other users. This vulnerability is fixed in 2.0.6.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
Affected products
Ajax30 · BraveCMS-2.0Related CVEs — Ajax30 BraveCMS-2.0
In the same product, most dangerous first.
CVE-2026-35164HIGHBrave CMS Sffected by Unrestricted File Upload via CKEditor EndpointEPSS 0.7%CVE-2026-35047CRITICALBrave CMS has Unrestricted File Upload in BraveCMS via CKEditor EndpointEPSS 0.6%CVE-2026-35182HIGHMissing Authorization Privilege EscalationEPSS 0.3%CVE-2026-41576HIGHAjax30/BraveCMS-2.0: Stored HTML Injection in Contact Email via nl2br() and Unescaped Blade TemplateEPSS 0.3%CVE-2026-41524HIGHAjax30/BraveCMS-2.0: Stored XSS in Page / Article ContentEPSS 0.3%