GHSA-wprj-9cvc-5w37

## Summary Multiple payment plugin `list.json.php` endpoints lack authentication and authorization checks, allowing unauthenticated attackers to retrieve all payment transaction records including PayPal billing agreement IDs, Express Checkout tokens, Authorize.Net webhook payloads with transaction details, and Bitcoin payment records. This is the same class of vulnerability fixed in the Scheduler plugin (GHSA-j724-5c6c-68g5 / commit 83390ab1f) but the fix was not applied to the remaining 21 affected endpoints. ## Details The AVideo ObjectYPT admin CRUD pattern generates four endpoints per database table: `add.json.php`, `delete.json.php`, `list.json.php`, and an `index.php` page. In the payment plugins, `add.json.php` and `delete.json.php` correctly check `User::isAdmin()` before proceeding, but the `list.json.php` endpoints have no authorization check whatsoever. **PayPalYPT_log list endpoint** (`plugin/PayPalYPT/View/PayPalYPT_log/list.json.php:1-10`): ```php <?php require_once '../../../../videos/configuration.php'; require_once $global['systemRootPath'] . 'plugin/PayPalYPT/Objects/PayPalYPT_log.php'; header('Content-Type: application/json'); $rows = PayPalYPT_log::getAll(); $total = PayPalYPT_log::getTotal(); ?> {"data": <?php echo json_encode($rows); ?>, ...} ``` No `User::isAdmin()` check. The `getAll()` method (inherited from `ObjectYPT`) executes `SELECT * FROM PayPalYPT_log` returning all records. **Contrast with the sibling add endpoint** (`plugin/PayPalYPT/View/PayPalYPT_log/add.json.php:13-16`): ```php if (!User::isAdmin()) { $obj->msg = "You can't do this"; die(json_encode($obj)); } ``` The `configuration.php` bootstrap file performs no global authentication gating — it initializes the application framework but does not enforce auth. No `.htaccess` rules restrict access to plugin View directories. **Data model** (`plugin/PayPalYPT/Objects/PayPalYPT_log.php`): Each record contains `agreement_id`, `users_id`, `json` (full PayPal API respo