Quick answers
- Is CVE-2026-35182 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35182 being exploited in the wild.
- How severe is CVE-2026-35182?
- High severity, with a CVSS score of 8.8, published 6 April 2026.
- Which products and versions are affected?
- Ajax30 Bravecms >= 2.0.0, < 2.0.6.
- Is there a fix for CVE-2026-35182?
- 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-35182 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-35182?
- Check whether you run Ajax30 Bravecms 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
A missing authorization check exists in Brave CMS versions prior to 2.0.6 within the role update functionality. Specifically, the POST route for '/rights/update-role/{id}' in 'routes/web.php' fails to implement the 'checkUserPermissions:assign-user-roles' middleware. An authenticated attacker with low-level privileges can exploit this by sending a crafted POST request to the endpoint to modify their own 'role_id' or that of others. Successful exploitation results in vertical privilege escalation to 'Super Admin', granting full control over the CMS environment. The issue is resolved in version 2.0.6 by applying the appropriate middleware to the affected route.
Affected products
- Ajax30 BraveCMS-2.0 >= 2.0.0, < 2.0.6
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