AVideo: Unauthenticated Access to Payment Order Data via BlockonomicsYPT check.phpGHSA-3v7m-qg4x-58h9
LOWGHSA-3v7m-qg4x-58h9 is a low-severity (CVSS 3.7) CWE-862 vulnerability in wwbn/avideo. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-3v7m-qg4x-58h9.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
wwbn/avideoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | wwbn/avideo | all versions | No fix |
Affected Products
avideowwbnDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wwbn/avideo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of wwbn/avideo for GHSA-3v7m-qg4x-58h9. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-3v7m-qg4x-58h9 in your dependencies?
Find it across Packagist, including transitive dependencies.