Skip to main content
VulnerabilityPublished Updated

CVE-2026-93366: Bludit CMS · Insecure Direct Object Reference

Affects Bludit CMSSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
BluditBludit CMSAffected
  • <=3.22.0
  • <=4.0.0-beta-1
  • =0
Fixed in–
GitHubBludit CMSpkg:github/Bludit CMSOther threatsAffected
  • <=3.22.0
  • <=4.0.0-beta-1
  • =0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is available, restrict Author role permissions where possible and monitor access to AJAX endpoints. Avoid exposing these endpoints to untrusted users. Follow vendor updates for patches addressing this vulnerability.

Description

Bludit CMS through 3.22.0 contains an authorization bypass vulnerability that allows authenticated users with the Author role to enumerate and delete media files belonging to pages owned by other users, including administrators, by supplying arbitrary uuid parameters to unprotected AJAX endpoints. Attackers can retrieve page UUIDs for all users via the content-get-list endpoint and then submit crafted POST requests to the list-images and delete-image endpoints in bl-kernel/ajax/ to access and destroy media files outside their own pages, bypassing the IMAGE_RESTRICT isolation control.

References

Community reviews

Loading reviews…