bug: CLI RestoreCommand passes wrong arguments to RestoreEngine #71

New Issue

2026-06-21T23:00:54Z

jmiller commented

2026-06-21 23:00:54 +00:00

Severity: CRITICAL

RestoreCommand at line 89 calls $engine->restore($record->absolute_path, $record->backup_type) — passing a string filepath as the int $recordId parameter and a backup type string as bool $restoreFiles. PHP coerces the filepath to int 0, the engine queries WHERE id = 0, finds nothing, and returns failure.

The CLI restore command is completely broken.

Fix

$result = $engine->restore($recordId);

File

plg_console_mokosuitebackup/src/Command/RestoreCommand.php:89

## Severity: CRITICAL `RestoreCommand` at line 89 calls `$engine->restore($record->absolute_path, $record->backup_type)` — passing a string filepath as the `int $recordId` parameter and a backup type string as `bool $restoreFiles`. PHP coerces the filepath to `int 0`, the engine queries `WHERE id = 0`, finds nothing, and returns failure. **The CLI restore command is completely broken.** ## Fix ```php $result = $engine->restore($recordId); ``` ## File - `plg_console_mokosuitebackup/src/Command/RestoreCommand.php:89`

jmiller added the component: engine label 2026-06-21 23:00:54 +00:00

jmiller referenced this issue

2026-06-21 23:04:13 +00:00

test: Deep dive audit — verify and fix all findings #81

jmiller referenced this issue from a commit

2026-06-21 23:09:43 +00:00

fix: critical and high audit findings (#81)

jmiller referenced a pull request that will close this issue

2026-06-21 23:09:56 +00:00

fix: Critical and high audit findings (#81) #83

jmiller closed this issue

2026-06-21 23:10:23 +00:00