CVE-2026-11511

Bolt CMS versions 3.7.0 and earlier contain a chain of vulnerabilities that allow an authenticated user to achieve remote code execution. A user with valid credentials can inject arbitrary PHP code into the displayname field, which is rendered unsanitized in backend templates. The attacker can then rename session files to a public path with a .php extension, creating a web shell. The vendor announced end-of-life for Bolt 3 after 31 December 2021.

Bolt CMS version 5.1.12 and below contains a vulnerability that allows an authenticated user with ROLE_EDITOR privileges to upload and rename a malicious file, leading to remote code execution.

Bolt CMS renders content field values through Twig's full application-level Environment with no SandboxExtension registered. In src/Entity/Field.php, getTwigValue calls shouldBeRenderedAsTwig, which gates rendering only on the field definition's allow_twig flag and a regex, then compiles and renders the raw value without sandboxing.

Bolt CMS up to version 3.7.0 contains an SQL injection vulnerability in the 'order' parameter of content listing pages. An authenticated attacker with low privileges can exploit this via the OrderDirective component, allowing extraction of sensitive information.

Bolt CMS version 4.2 and earlier is vulnerable to Remote Code Execution. Unsafe theme rendering allows an authenticated attacker to edit the theme and inject server-side template injection, leading to remote code execution.