CVE-2026-35448: WWBN AVideo Provides Unauthenticated Access to Payment Order Data via BlockonomicsYPT check.php

Published Apr 4, 2026
·
Updated

Summary

The BlockonomicsYPT plugin's check.php endpoint returns payment order data for any Bitcoin address without requiring authentication. The endpoint was designed as an AJAX polling helper for the authenticated invoice.php page, but it performs no access control checks of its own. Since Bitcoin addresses are publicly visible on the blockchain, an attacker can query payment records for any address used on the platform.

Details

In plugin/BlockonomicsYPT/check.php at lines 20-30, the endpoint accepts a Bitcoin address and returns the corresponding order data:

php $addr = $GET['addr']; $order = new BlockonomicsOrder(0); $obj = $order->getFromAddressFromDb($addr); die(jsonencode($obj));

There is no authentication check. The endpoint does not verify that the requesting user is logged in, nor does it verify that the requesting user owns the order associated with the given address.

The response includes: - User ID of the buyer - Total payment value - Currency - BTC amounts (expected and received) - Transaction ID - Payment status

The invoice.php page that was designed to consume this endpoint does require authentication, but check.php itself does not inherit or enforce that requirement.

Bitcoin addresses are publicly queryable on the blockchain, so an attacker does not need to guess them. Addresses associated with the platform can be discovered by monitoring blockchain transactions to known platform wallets.

The BlockonomicsYPT plugin is tagged as deprecated by the AVideo project, but remains available and functional in current installations.

Proof of Concept

bash Query payment data for a known Bitcoin address without authentication curl "https://your-avideo-instance.com/plugin/BlockonomicsYPT/check.php?addr=1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa"

Example response:

json { "id": 42, "usersid": 15, "value": "29.99", "currency": "USD", "btcvalue": "0.00085", "btcreceived": "0.00085", "txid": "abc123def456...", "status": "confirmed", "created": "2025-01-15 10:30:00" }

No session cookie or API key is required.

Impact

- Unauthenticated disclosure of payment order data including user IDs, amounts, and transaction details - Bitcoin addresses are publicly discoverable on the blockchain - Links on-chain transactions to specific platform user IDs - Privacy violation for users who made cryptocurrency payments on the platform - Plugin is deprecated but still functional in existing deployments

Recommended Fix

Add an authentication check at plugin/BlockonomicsYPT/check.php:17:

php if (!User::isLogged()) { echo jsonencode(["error" => "Login required"]); exit; }

--- Found by aisafe.io

Other sources

WWBN AVideo is an open source video platform. In versions 26.0 and prior, the BlockonomicsYPT plugin's check.php endpoint returns payment order data for any Bitcoin address without requiring authentication. The endpoint was designed as an AJAX polling helper for the authenticated invoice.php page, but it performs no access control checks of its own. Since Bitcoin addresses are publicly visible on the blockchain, an attacker can query payment records for any address used on the platform.

MITRE

Affected Software

2 affected components
composer/wwbn/avideo<=26.0
WWBN AVideo<=26.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    At plugin/BlockonomicsYPT/check.php (around line 17 and lines 20-30 per the report), add an authentication check so the endpoint returns the payment order data only to logged-in users. The material specifically indicates that in versions 26.0 and prior the endpoint returns order data for any Bitcoin address without requiring authentication; implement the missing access control check (e.g., ensure the endpoint checks User::isLogged() before calling getFromAddressFromDb and before returning JSON).

    BlockonomicsYPT plugin (plugin/BlockonomicsYPT/check.php) authentication/access control = enforce login before returning payment order data

Event History

Apr 4, 2026
Advisory Published
via GitHub·06:15 AM
Data Sourced
via GitHub·06:15 AM
DescriptionSeverityWeaknessAffected Software
Apr 6, 2026
CVE Published
via MITRE·09:45 PM
Data Sourced
via MITRE·09:45 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:16 PM
Affected Software

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203