Bludit CVE-2026-107190: Author File Deletion
CERT Polska disclosed path traversal in Bludit 3.22.0. An Author can delete other files and administrator pages. We explain risk and mitigation.
- AUTHOR
- Karol Rapacz / CEO Breachroad · OSCP · PNPT
- PUBLISHED
- 17 November 2026
- READING TIME
- 19 min read
- TOPIC
- Vulnerabilities and CVEs
On 17 November 2026, CERT Polska disclosed CVE-2026-107190, a path-traversal vulnerability in the Bludit content management system. The flaw affects page deletion and lets an authenticated user with the Author role influence the path passed to a recursive filesystem deletion operation.
According to the official English-language CERT Polska advisory, an author can set the UUID field of their page to contain parent-directory traversal sequences. The value is stored without adequate validation. When the page is deleted, Pages::delete() constructs a path from that UUID and passes it to Filesystem::deleteRecursive() without verifying that the normalised path remains inside the approved directory.
The result can be deletion of files that do not belong to the author, including administrator pages, and the site may become unusable. CERT confirmed the issue in Bludit 3.22.0. Attempts to contact the developer were unsuccessful, so other versions may be affected, but that wider scope has not been publicly confirmed.
Why this vulnerability matters
CVE-2026-107190 is not unauthenticated RCE and should not be reported as such. It requires an Author account. That does not make it low risk. In a publishing workflow, Author is commonly assigned to employees, freelancers and partners who should manage their own content but not the site’s complete filesystem.
The trust boundary lies between “delete my page” and “delete a resource selected through a manipulated path”. If one compromised Author account can destroy site availability or remove administrator content, the account has gained impact well beyond its intended role.
Risk increases when:
- authors use passwords without MFA;
- accounts are shared by multiple people;
- the administration panel is publicly reachable;
- backups reside on the same server and within reach of the application process;
- the PHP process has broad filesystem permissions;
- mass deletion and UUID changes are not monitored;
- no tested recovery environment or RTO exists;
- a weaker integration or plugin can create Author accounts.
How the control failure works
A filesystem path is security-sensitive data. The application may intend to delete a directory for one page, but it cannot trust a previously stored value when a user influenced it. Validation on write is useful, but a sensitive operation should enforce the boundary again immediately before deletion.
A safe algorithm should:
- establish a fixed base directory;
- reject identifiers outside an approved format;
- build the path with safe platform functions;
- canonicalise separators and parent elements;
- prove that the result is a child of the base directory;
- reject symbolic links or mount points that escape the boundary;
- use operating-system permissions that prevent deletion of unrelated resources.
A text check that a path “starts with” the directory name can be insufficient. Platform-specific separators, encoding, symbolic links and paths sharing a common prefix can defeat a naive comparison. Canonicalisation and component-aware containment are required.
What is confirmed and what remains unknown
The mechanism in Bludit 3.22.0, the Author-role prerequisite and arbitrary deletion within the application’s filesystem reach—including administrator pages—are confirmed. CERT Polska coordinated disclosure after a report by Wojciech Ciemski.
The advisory does not report active exploitation in production. It does not confirm which other versions are affected or identify a vendor-fixed version. The public record does not describe data theft, code execution or operating-system compromise.
That boundary is important. File deletion can cause serious loss of availability, but it should not automatically become “RCE” in a headline. Conversely, no reported exploitation does not justify ignoring the flaw when Author accounts exist.
Immediate inventory
Administrators should determine whether Bludit is present anywhere in the environment. Search application inventories, container images, web-server configuration, hosting panels, repositories and migration copies. A campaign subdomain created years ago may remain online without a clear owner.
Then establish:
- the version on each node;
- every account and role;
- the most recent login date for each author;
- whether administration is public;
- the PHP system user’s filesystem permissions;
- backup location and whether the application can modify it;
- log retention and page-change history;
- the business and technical owners.
If anomalies are visible, do not delete files or accounts before preserving evidence. Capture logs, configuration, process information and filesystem metadata first.
Mitigation without a confirmed vendor patch
At publication time CERT does not identify a fixed vendor release. Temporarily disabling authoring or removing the administration panel from the Internet may be the safest decision, depending on business criticality. If authors do not need to publish immediately, suspending Author accounts removes a prerequisite.
Layered temporary controls include:
- removing Author from inactive and external accounts;
- enforcing unique passwords and MFA through the available identity layer;
- restricting the panel through VPN, allowlisting or an authenticating reverse proxy;
- blocking direct UUID modification in the UI and API;
- monitoring UUID writes and deletion actions;
- reducing the process’s rights to essential directories;
- moving backups outside the application account’s reach;
- preparing a static emergency copy of essential pages.
A WAF may detect common traversal sequences but is not a complete fix. A value may be encoded, stored earlier or delivered through another path. The strongest boundary belongs in the application and filesystem.
Operating-system permissions
A CMS generally needs write access to content, cache and upload directories. It should not be able to delete server configuration, backups, keys, other applications or system directories. Separate the code owner from the PHP runtime user and mount code read-only where the architecture permits.
In a container, use a read-only root filesystem with dedicated data volumes, drop unnecessary capabilities and run as a non-privileged user. On conventional hosting, use a separate system account for each site. One vulnerable application must not be able to delete a neighbouring domain’s data.
This containment does not remove the CVE—the author may still affect content within the permitted data directory—but it reduces the maximum impact. It is defence in depth: an application defect should not automatically grant reach across the entire filesystem.
Hunting for exploitation
Preserve HTTP and application logs, login history, panel audit events and filesystem metadata. Useful signals include:
- UUID changes containing unusual separators, encoding or parent elements;
- a page created and rapidly deleted by the same account;
- multiple deletion operations after a login from a new address or device;
- files disappearing outside the author’s page directory;
- application errors caused by missing configuration or administrator pages;
- an Author login after a long period of inactivity;
- a role change immediately before deletion;
- content deletion coinciding with access to backup locations;
- timestamp or log tampering.
The absence of an application log entry does not exclude the action. Recursive deletion may remove files required for local logging. Security logs should therefore be exported to an external append-only system rather than retained only on the affected host.
Recovery after a destructive event
A backup has value only after a successful restore test. Copies should be separated from the application account, versioned and protected against rapid deletion. A small site can also maintain a static export that provides an emergency presence while the CMS is investigated.
The recovery plan should define:
- who authorises shutdown;
- how evidence is preserved before restore;
- which backup is considered clean;
- how passwords and sessions are rotated;
- how code and content integrity are verified;
- how forms, analytics and integrations are tested;
- when Author accounts are restored;
- how downtime is communicated.
Our 3-2-1 backup and ransomware-resilience guide develops this model. The immediate threat here is deletion rather than encryption, but backup isolation is the same requirement.
A safe retest
Testing belongs on a controlled copy with an explicitly created Author account and synthetic files. The goal is to prove that the user can remove only their own resource inside the approved directory, and that every canonicalised path remains within that boundary.
Do not test the vulnerability on a public installation you do not own. Even an apparently harmless attempt may delete data. A version-detection scanner should never send a destructive payload.
Once a fix is available, retesting should cover Windows and Unix separators, alternate encodings, repeated parent components, symbolic links and previously stored values. Regression also matters: an author must still be able to delete their own page safely.
The exercise fits within a web application penetration test or an IT security audit.
The lesson for CMS developers
A UUID is a logical identifier, not a filesystem path. Secure architecture should not let a user-controlled identifier determine the physical location to be deleted. The application can map the UUID to an internal record and generate a directory name from a restricted alphabet instead of using raw input.
Destructive operations should be narrow, auditable and recoverable. Soft deletion, a deletion queue and retention window make it possible to restore content after user error or attack. Physical file deletion can run in a separate process that enforces the boundary again.
Unit tests should cover canonicalised paths, while integration tests should exercise real filesystem permissions. Our secure file upload guide relies on the same principle: a user-provided name must never directly select a sensitive filesystem path.
A 24/7/30 action plan
Within 24 hours: find every installation, verify versions and Author accounts, restrict the public panel, preserve logs and test backup availability. If authoring is not required, disable it until a credible fix is available.
Within seven days: contact the vendor or implementation partner, prepare a controlled environment, review UUID and deletion history, reduce process permissions and perform a restore test. Escalate to full incident response when anomalies are found.
Within 30 days: deploy a fix when available or plan migration if the project cannot provide a secure maintenance path. Add an external audit trail, isolated copies, periodic role review and recurring restore tests.
Source facts and Breachroad conclusions
CERT Polska confirms path traversal in Bludit 3.22.0, the Author-role requirement, use of UUID in recursive deletion and the ability to remove other files and administrator pages. It also confirms unsuccessful vendor contact and uncertainty about additional versions.
The layered mitigations, hunting patterns, recovery plan and 24/7/30 model are Breachroad recommendations. They are not a vendor patch announcement. Until remediation is confirmed, function and privilege restrictions remain temporary controls rather than a definitive fix.
Summary
CVE-2026-107190 demonstrates how an apparently limited account can become destructive when an application combines a user-influenced identifier with recursive deletion. Bludit owners should locate installations, restrict Author roles and administration, preserve telemetry and verify backup recovery.
The core rule is simple: after canonicalisation, every filesystem operation must remain within an explicitly permitted directory, while the application process holds minimum rights. Code validation and operating-system containment need to work together.


