Back to the CVE list
CVE-2026-56341

AVideo: Unauthenticated Access to Payment Log DataTables Endpoints Exposes Transaction Data, PayPal Tokens, and User Financial Records

CVSS score

7.5

EPSS probability

%0.5

Risk score

0.0

Published

6 mo ago

Patch status has not yet been verified

Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.

Impact on My Inventory

Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.

Checking session…

Vulnerability description

DayBreach CVE AI Research

CVE-2026-56341 has vendor, distribution, patch and security-source records on file. We can compare them and prepare an explanation linked to the evidence.

## 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`

IMPACT: Affected Products and Software

Affected Products

The following products are affected by CVE-2026-56341 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.

IDVENDORPRODUCTACTION
1packagistwwbn/avideo View
Total affected vendors: 1|Products: 1

RED HAT CSAF/VEX: Product Impact Check

Red Hat has not yet published a CSAF/VEX impact record for this CVE. This does not mean “not affected”.

SCORING: CVSS from Multiple Sources

CVSS Scores

The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.

SCOREVERSIONSEVERITYVECTORSOURCE
7.5CVSS 3.x—Vector not publishedGitHub Advisory
0.0CVSS 4.0—Vector not publishedGitHub Advisory

Patch and Remediation Guide

Solution & Remediation Advisory

Patch status unknown

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Confirm the affected product and version against the source evidence above.
Restrict access to internet-facing services and apply network segmentation.
Until a patch is confirmed, follow the vendor advisory; do not read an unknown status as “no patch”.
Monitor server logs and network endpoints for signs of anomalous execution.

Public exploit and active exploitation status

Verified exploit intelligence

No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.

Weakness Classification and Attack Patterns (CWE & CAPEC)

CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-56341 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-56341 weaknesses.

Attack Vector and Accessibility

ExposureAğ üzerinden
PermissionsGerekmiyor
UserGerekmiyor

Official Sources and Advisories

CVSS Vector Radar Chart

7.5 / 10
Attack VectorNetworkComplexityLowPrivilegesNoneUser Interact.NoneConfidentialityLowIntegrityNoneAvailabilityNone

Vulnerability Scoring Details

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone required
User InteractionNone required
Confidentiality (Gizlilik)Low
Integrity (Bütünlük)None
Availability (Erişilebilirlik)None

Yama durumu bilinmiyor

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Follow the vendor

Weakness Type (CWE & CAPEC)

Similar Vulnerabilities

Get this vulnerability through the API

Affected products, version ranges, exploitation status and patch information in a single request, with a free key.

curl -H "x-api-key: $DAYBREACH_API_KEY" \
  "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-56341"