Quick answers
- Is CVE-2026-95153 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-95153 being exploited in the wild.
- How severe is CVE-2026-95153?
- Informational severity, published 6 October 2026.
- Which products and versions are affected?
- Bludit CMS 3.22.0.
- Is there a fix for CVE-2026-95153?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-95153 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-95153?
- Check whether you run Bludit CMS 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
The /admin/ajax/clippy and /admin/ajax/save-as-draft endpoints in Bludit 3.22.0 lack role-based authorization checks, allowing authenticated users to enumerate and manipulate articles belonging to other authors. An author-level user can send GET requests to /admin/ajax/clippy?query= to retrieve UUIDs of all autosave-type draft articles, then use those UUIDs in POST requests to /admin/ajax/save-as-draft to modify and change article status to published. No checkRole() validation is performed on article ownership.
Affected products
- Bludit Bludit CMS 3.22.0
Timeline
- 2026-10-06: disclosed