Pico 3.0.0-alpha.2 Exploit ⏰

If an exploit can inject malicious code into a Markdown file's YAML front matter that is then rendered via an unsanitized Twig filter, the server may execute arbitrary PHP commands. The Impact: Full server compromise. 3. Insecure Plugin Hooks

Pico has traditionally been praised for its simplicity—no database, just Markdown files. The leap to version 3.0 introduced a revamped plugin system and internal routing logic. While these features increase flexibility, they also expanded the attack surface, particularly regarding how the CMS handles user-inputted file paths and plugin configurations. Known Vulnerability Vectors 1. Path Traversal & Local File Inclusion (LFI)

Ensure the webserver user has the absolute minimum permissions required to read the content and themes folders. Pico 3.0.0-alpha.2 Exploit

If you are currently testing Pico 3.0.0-alpha.2, it is vital to remember that To secure your installation:

If successful, this allows an unauthorized user to read sensitive system files like /etc/passwd or the CMS's own configuration files ( config/config.yml ), which may contain API keys or secret salts. 2. Remote Code Execution (RCE) via Twig Templates If an exploit can inject malicious code into

An attacker might attempt to bypass the content directory restrictions by using ../ sequences in the URI.

The most prominent concern in the 3.0.0-alpha.2 build involves the way the core engine resolves content folders. Because Pico relies on the file system rather than a SQL database, any weakness in the sanitization of URL parameters can lead to Path Traversal. Insecure Plugin Hooks Pico has traditionally been praised

Ensure debug mode is turned off in your PHP configuration to prevent sensitive path leakage during a crash.