CVE-2026-56341: AVideo Unauthenticated Access To Payment Log Vulnerability

HIGH
Advisory Identifier: GHSA-wprj-9cvc-5w37
CVSS 7.5
CWE-862 CWE-200
Published
Advisory Summary

CVE-2026-56341 is a HIGH (CVSS 7.5) unauthenticated access to payment log vulnerability (CWE-862: Missing Authorization) affecting AVideo libraries in the Packagist ecosystem. The issue involves unauthenticated access to payment log datatables endpoints exposes transaction data, paypal tokens, and user financial records. Remediation is available in the latest vendor maintenance releases.

CVE-2026-56341 at a Glance

CVE Identifier CVE-2026-56341
GHSA Identifier GHSA-wprj-9cvc-5w37
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-862: Missing Authorization
Affected Product AVideo
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-56341

To remediate this vulnerability, upgrade all affected AVideo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

wwbn/avideo fixed: Latest secure release
Upgrade wwbn/avideo to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for wwbn/avideo

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-56341, inspect your project dependencies for AVideo:

inspect dependencies for wwbn/avideo

Analyze the terminal output to locate any version of AVideo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-862: Missing Authorization, where the product does not perform an authorization check when an actor attempts to access a resource or perform an action. In AVideo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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 payloads - `plugin/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.php` endpoints 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: 1. `plugin/PayPalYPT/View/PayPalYPT_log/list.json.php` 2. `plugin/AuthorizeNet/View/Anet_webhook_log/list.json.php` 3. `plugin/BTCPayments/View/Btc_payments/list.json.php` 4. `plugin/AI/View/Ai_responses/list.json.php` 5. `plugin/AI/View/Ai_metatags_responses/list.json.php` 6. `plugin/AI/View/Ai_transcribe_responses/list.json.php` 7. `plugin/Live/view/Live_servers/list.json.php` 8. `plugin/Live/view/Live_schedule/list.json.php` 9. `plugin/Live/view/Live_restreams_logs/list.json.php` 10. `plugin/SocialMediaPublisher/View/Publisher_schedule/list.json.php` 11. `plugin/SocialMediaPublisher/View/Publisher_social_medias/list.json.php` 12. `plugin/Meet/View/Meet_join_log/list.json.php` 13. `plugin/Meet/View/Meet_schedule_has_users_groups/list.json.php` 14. `plugin/PlayLists/View/Playlists_schedules/list.json.php` 15. `plugin/UserConnections/View/Users_connections/list.json.php` 16. `plugin/UserNotifications/View/User_notifications/list.json.php` 17. `plugin/VideosStatistics/View/Statistics/list.json.php` 18. `plugin/VideoTags/View/Tags_subscriptions/list.json.php` 19. `plugin/CustomizeUser/View/Categories_has_users_groups/list.json.php` 20. `plugin/CustomizeUser/View/Users_extra_info/list.json.php` 21. `plugin/ImageGallery/list.json.php`

CVE-2026-56341 Affected AVideo Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
wwbn/avideo
Packagist
≤ 26.0

References

Frequently Asked Questions

What is CVE-2026-56341?
CVE-2026-56341 is a security vulnerability in AVideo involving Unauthenticated Access to Payment Log DataTables Endpoints Exposes Transaction Data, PayPal Tokens, and User Financial Records under CWE-862: Missing Authorization.
Which AVideo versions are affected?
Affected versions include releases prior to current release patches across affected packages: wwbn/avideo.
What version fixes CVE-2026-56341?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is wwbn/avideo affected?
Yes, wwbn/avideo is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-56341?
CVE-2026-56341 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-56341?
CVE-2026-56341 is classified under CWE-862: Missing Authorization (The product does not perform an authorization check when an actor attempts to access a resource or perform an action.).
How can I check Packagist dependencies for CVE-2026-56341?
Run the dependency tree command: 'inspect dependencies for wwbn/avideo'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wprj-9cvc-5w37",
  "modified" : "2026-09-09T23:53:42Z",
  "published" : "2026-03-29T15:40:52Z",
  "aliases" : [ "CVE-2026-56341" ],
  "summary" : "AVideo: Unauthenticated Access to Payment Log DataTables Endpoints Exposes Transaction Data, PayPal Tokens, and User Financial Records",
  "details" : "## Summary\n\nMultiple 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.\n\n## Details\n\nThe 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.\n\n**PayPalYPT_log list endpoint** (`plugin/PayPalYPT/View/PayPalYPT_log/list.json.php:1-10`):\n```php\n<?php\nrequire_once '../../../../videos/configuration.php';\nrequire_once $global['systemRootPath'] . 'plugin/PayPalYPT/Objects/PayPalYPT_log.php';\nheader('Content-Type: application/json');\n\n$rows = PayPalYPT_log::getAll();\n$total = PayPalYPT_log::getTotal();\n?>\n{\"data\": <?php echo json_encode($rows); ?>, ...}\n```\n\nNo `User::isAdmin()` check. The `getAll()` method (inherited from `ObjectYPT`) executes `SELECT * FROM PayPalYPT_log` returning all records.\n\n**Contrast with the sibling add endpoint** (`plugin/PayPalYPT/View/PayPalYPT_log/add.json.php:13-16`):\n```php\nif (!User::isAdmin()) {\n    $obj->msg = \"You can't do this\";\n    die(json_encode($obj));\n}\n```\n\nThe `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.\n\n**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).\n\nThe identical pattern exists in:\n- `plugin/AuthorizeNet/View/Anet_webhook_log/list.json.php` — full Authorize.Net webhook payloads\n- `plugin/BTCPayments/View/Btc_payments/list.json.php` — Bitcoin transaction identifiers and amounts\n\nThis 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.\n\n## PoC\n\n**Step 1 — Dump PayPal transaction logs (unauthenticated):**\n```bash\ncurl -s 'https://target.com/plugin/PayPalYPT/View/PayPalYPT_log/list.json.php'\n```\nReturns all PayPal transaction records including agreement IDs, tokens, payment amounts, user IDs, and full PayPal API JSON responses.\n\n**Step 2 — Dump Authorize.Net webhook logs (unauthenticated):**\n```bash\ncurl -s 'https://target.com/plugin/AuthorizeNet/View/Anet_webhook_log/list.json.php'\n```\nReturns all Authorize.Net webhook payloads including transaction IDs, event types, and payment details.\n\n**Step 3 — Dump Bitcoin payment records (unauthenticated):**\n```bash\ncurl -s 'https://target.com/plugin/BTCPayments/View/Btc_payments/list.json.php'\n```\nReturns all Bitcoin transaction identifiers, BTC amounts, and store identifiers.\n\n**Step 4 — Confirm sibling endpoints ARE protected:**\n```bash\ncurl -s -X POST 'https://target.com/plugin/PayPalYPT/View/PayPalYPT_log/add.json.php'\n# Returns: {\"error\":true,\"msg\":\"You can't do this\"}\n```\n\n## Impact\n\n- **Financial data exposure:** Unauthenticated attackers can retrieve all payment transaction records across PayPal, Authorize.Net, and Bitcoin payment providers.\n- **Token leakage:** PayPal Express Checkout tokens and billing agreement IDs are exposed, potentially enabling payment manipulation or account correlation.\n- **PII leakage:** Transaction records contain user ID mappings, payment amounts, and full API responses that may include payer email addresses and names.\n- **Broad scope:** 21 total `list.json.php` endpoints lack auth, also exposing live streaming server infrastructure (`Live_servers`), user connection data, meeting participation logs, and AI transcription responses.\n- **Zero interaction required:** No authentication, no user interaction — a single GET request dumps the entire table.\n\n## Recommended Fix\n\nAdd `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:\n\n```php\nif (!User::isAdmin()) {\n    $obj = new stdClass();\n    $obj->error = true;\n    $obj->msg = \"You can't do this\";\n    die(json_encode($obj));\n}\n```\n\nThe full list of files requiring this fix:\n\n1. `plugin/PayPalYPT/View/PayPalYPT_log/list.json.php`\n2. `plugin/AuthorizeNet/View/Anet_webhook_log/list.json.php`\n3. `plugin/BTCPayments/View/Btc_payments/list.json.php`\n4. `plugin/AI/View/Ai_responses/list.json.php`\n5. `plugin/AI/View/Ai_metatags_responses/list.json.php`\n6. `plugin/AI/View/Ai_transcribe_responses/list.json.php`\n7. `plugin/Live/view/Live_servers/list.json.php`\n8. `plugin/Live/view/Live_schedule/list.json.php`\n9. `plugin/Live/view/Live_restreams_logs/list.json.php`\n10. `plugin/SocialMediaPublisher/View/Publisher_schedule/list.json.php`\n11. `plugin/SocialMediaPublisher/View/Publisher_social_medias/list.json.php`\n12. `plugin/Meet/View/Meet_join_log/list.json.php`\n13. `plugin/Meet/View/Meet_schedule_has_users_groups/list.json.php`\n14. `plugin/PlayLists/View/Playlists_schedules/list.json.php`\n15. `plugin/UserConnections/View/Users_connections/list.json.php`\n16. `plugin/UserNotifications/View/User_notifications/list.json.php`\n17. `plugin/VideosStatistics/View/Statistics/list.json.php`\n18. `plugin/VideoTags/View/Tags_subscriptions/list.json.php`\n19. `plugin/CustomizeUser/View/Categories_has_users_groups/list.json.php`\n20. `plugin/CustomizeUser/View/Users_extra_info/list.json.php`\n21. `plugin/ImageGallery/list.json.php`",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "wwbn/avideo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "26.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/WWBN/AVideo/security/advisories/GHSA-wprj-9cvc-5w37"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-56341"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/WWBN/AVideo/commit/1729a955f8de7e26552eb728b3d1e6f4b1b9352e"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/WWBN/AVideo"
  }, {
    "type" : "ADVISORY",
    "url" : "https://github.com/advisories/GHSA-j724-5c6c-68g5"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/avideo-unauthenticated-access-to-payment-log-datatables-endpoints-via-list-json-php"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-862" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-29T15:40:52Z",
    "nvd_published_at" : null
  }
}