GHSA-3V7M-QG4X-58H9

Vulnerability from github – Published: 2026-04-04 06:15 – Updated: 2026-04-07 14:20
VLAI?
Summary
AVideo: Unauthenticated Access to Payment Order Data via BlockonomicsYPT check.php
Details

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:

$addr = $_GET['addr'];
$order = new BlockonomicsOrder(0);
$obj = $order->getFromAddressFromDb($addr);
die(json_encode($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

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

Example response:

{
  "id": 42,
  "users_id": 15,
  "value": "29.99",
  "currency": "USD",
  "btc_value": "0.00085",
  "btc_received": "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:

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

Found by aisafe.io

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "wwbn/avideo"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "26.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-35448"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-04-04T06:15:37Z",
    "nvd_published_at": "2026-04-06T22:16:23Z",
    "severity": "LOW"
  },
  "details": "## Summary\n\nThe BlockonomicsYPT plugin\u0027s `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.\n\n## Details\n\nIn `plugin/BlockonomicsYPT/check.php` at lines 20-30, the endpoint accepts a Bitcoin address and returns the corresponding order data:\n\n```php\n$addr = $_GET[\u0027addr\u0027];\n$order = new BlockonomicsOrder(0);\n$obj = $order-\u003egetFromAddressFromDb($addr);\ndie(json_encode($obj));\n```\n\nThere 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.\n\nThe response includes:\n- User ID of the buyer\n- Total payment value\n- Currency\n- BTC amounts (expected and received)\n- Transaction ID\n- Payment status\n\nThe `invoice.php` page that was designed to consume this endpoint does require authentication, but `check.php` itself does not inherit or enforce that requirement.\n\nBitcoin 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.\n\nThe BlockonomicsYPT plugin is tagged as deprecated by the AVideo project, but remains available and functional in current installations.\n\n## Proof of Concept\n\n```bash\n# Query payment data for a known Bitcoin address without authentication\ncurl \"https://your-avideo-instance.com/plugin/BlockonomicsYPT/check.php?addr=1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa\"\n```\n\nExample response:\n\n```json\n{\n  \"id\": 42,\n  \"users_id\": 15,\n  \"value\": \"29.99\",\n  \"currency\": \"USD\",\n  \"btc_value\": \"0.00085\",\n  \"btc_received\": \"0.00085\",\n  \"txid\": \"abc123def456...\",\n  \"status\": \"confirmed\",\n  \"created\": \"2025-01-15 10:30:00\"\n}\n```\n\nNo session cookie or API key is required.\n\n## Impact\n\n- Unauthenticated disclosure of payment order data including user IDs, amounts, and transaction details\n- Bitcoin addresses are publicly discoverable on the blockchain\n- Links on-chain transactions to specific platform user IDs\n- Privacy violation for users who made cryptocurrency payments on the platform\n- Plugin is deprecated but still functional in existing deployments\n\n## Recommended Fix\n\nAdd an authentication check at `plugin/BlockonomicsYPT/check.php:17`:\n\n```php\nif (!User::isLogged()) {\n    echo json_encode([\"error\" =\u003e \"Login required\"]);\n    exit;\n}\n```\n\n---\n*Found by [aisafe.io](https://aisafe.io)*",
  "id": "GHSA-3v7m-qg4x-58h9",
  "modified": "2026-04-07T14:20:43Z",
  "published": "2026-04-04T06:15:37Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-3v7m-qg4x-58h9"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-35448"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/WWBN/AVideo"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "AVideo: Unauthenticated Access to Payment Order Data via BlockonomicsYPT check.php"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…