CVE
Bludit arbitrary file deletion via page deletion feature
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:H/SC:N/SI:L/SA:N
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects Bludit; confirmed only in version 3.22.0, may affect other versions.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Bludit, a content management system, has a path traversal flaw in its page deletion feature. A remote attacker with a low-privilege Author account can set a page's UUID to include path traversal sequences, and when that page is deleted, files outside the intended directory can be removed, including admin pages, which can make the site unusable.
Written by a model from the sources below. Verify against them.
Original description
Bludit is vulnerable to Path Traversal in the page deletion functionality. An authenticated user with the Author role can set the UUID field of their own page to contain path traversal sequences (.. and path separators), which are saved without proper validation. When the page is deleted, Pages::delete() passes the path constructed from this UUID to Filesystem::deleteRecursive() without verifying that it still points to an allowed directory, allowing the attacker to delete any files, even not belonging to them. Critically, it is possible to delete admin pages and render the site unusable.
Because vendor contact attempts were unsuccessful, the vulnerability has only been confirmed in version 3.22.0 but may also affect other versions.
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7/10CVSS 7.0
- No patch5/5No patch listed yet
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affects Bludit; confirmed only in version 3.22.0, may affect other versions.Workaround: The checked facts give no workaround or mitigation. Consult the vendor's advisory for guidance while no fix is listed.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-107190 (Path Traversal in Bludit), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-107190 (entry last updated 2026-11-17):
Affected:
- Bludit Bludit: versions 3.22.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affects Bludit; confirmed only in version 3.22.0, may affect other versions. (source: https://cert.pl/posts/2026/11/CVE-2026-107190/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-107190 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-107190 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://cert.pl/posts/2026/11/CVE-2026-107190
- https://github.com/bludit/bludit/releases#release-3.22.0
- https://cert.pl/posts/2026/11/CVE-2026-107190/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-107190
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-107190"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- bludit
3.22.0
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-107190
Is CVE-2026-107190 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The advisory title names a path traversal flaw in Bludit. The checked facts give no details on what an attacker could reach or do.Source: cert.pl
Which versions are affected by CVE-2026-107190?
bludit: version 3.22.0.Source: cve.now feed data
Am I affected, and how do I check?
The vulnerability was confirmed only in Bludit version 3.22.0, but the advisory says other versions may also be affected. To check, look up the installed Bludit version and compare it with 3.22.0 and the vendor's advisory, since the checked facts do not rule out other versions.Source: cert.pl
How do I fix CVE-2026-107190?
The checked facts list no fixed version and no vendor patch IDs. Check the vendor's advisory for an update before deciding on next steps.Source: cert.pl
What if there's no patch?
The checked facts give no workaround or mitigation. Consult the vendor's advisory for guidance while no fix is listed.Source: cert.pl