Skip to main content
VulnerabilityPublished

CVE-2026-95153: Bludit CMS · Information Exposure

Affects bluditSource GCVE Database

0
Compare
Authoritative record:CVE-2026-95153· Medium 4.9

Not known to be exploited · CVSS 4.9 Medium.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 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 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubbludit/bluditpkg:github/bludit/bluditOther threatsAffected
  • =3.22.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 a patch is available, restrict access to the affected endpoints to trusted users only and monitor for suspicious activity involving these endpoints.

Description

Bludit CMS version 3.22.0 contains a vulnerability that allows a remote attacker with high privileges to obtain sensitive information via the /admin/ajax/clippy and /admin/ajax/save-as-draft endpoints. The vulnerability does not require user interaction but requires privileges. The impact is limited to confidentiality without affecting integrity or availability.

References

Community reviews

Loading reviews…