Summary
AVideo up to version 26.0 exposes multiple payment-related list.json.php endpoints without any authorization checks.
Unauthenticated attackers can query these endpoints directly to harvest sensitive payment transaction data, including PayPal tokens, webhooks, and Bitcoin transaction records.
Affected context
This vulnerability occurs in AVideo deployments using the bundled or third-party payment plugins that expose list.json.php endpoints.
The issue manifests when these plugin endpoints are reachable over the network and are not protected by any access control or authentication middleware.
Systems where payment plugins are enabled in production and accessible from the internet are at particular risk of exposing user financial records and associated metadata.
Exploit preconditions
- Attack surface: Publicly accessible web endpoints in AVideo payment plugins
- Required access: No authentication or user account required; network access to the AVideo instance is sufficient
- Trigger point: Direct HTTP GET requests to exposed list.json.php endpoints in payment-related plugins
- Why exploitation is possible: The endpoints lack authorization checks, so the application does not verify the caller's identity or role before returning payment transaction data
Why this happens
The core issue is the absence of authorization enforcement on sensitive payment plugin endpoints, aligning with CWE-862: Missing Authorization.
The list.json.php scripts are implemented to return transaction records, tokens, and webhook data but are invoked without verifying whether a request is associated with an authenticated or privileged user.
This insecure pattern effectively treats all incoming requests as trusted, conflating public and sensitive resources and bypassing any notion of least privilege for access to financial data.
Potential impact
- Exposure of PayPal tokens and agreement IDs that could be used in downstream fraud or account linkage attacks
- Disclosure of Authorize.Net webhook payloads and API responses revealing transaction statuses and customer details
- Leakage of Bitcoin transaction records and related financial metadata for all users
- Unauthorized profiling of user purchasing behavior and subscription history
- Increased risk of targeted phishing or social engineering using harvested financial and transaction information
General mitigation guidance
Effective mitigation centers on enforcing strong, consistent authorization controls around all payment-related endpoints.
Recommended patterns include:
- Applying centralized access control middleware to all plugin routes, especially those returning financial or transactional data
- Restricting payment administration endpoints to authenticated users with explicit roles (e.g., admin, billing operators)
- Designing payment APIs using the principle of least privilege, ensuring responses are scoped to the requesting user's own data
- Avoiding direct exposure of raw transaction logs or provider tokens through web-accessible endpoints
- Segregating administrative payment interfaces onto restricted networks or behind VPNs where feasible
How teams detect issues like this
Organizations can identify similar issues using:
- Static review of route and controller definitions to ensure every payment-related endpoint passes through an authorization layer
- Security-focused code review checklists that flag any script or controller returning financial data without explicit access control
- Dynamic application security testing (DAST) and API fuzzing that probe payment plugin endpoints without credentials to detect data leakage
- Web server and application logs analysis to spot unauthenticated access patterns returning large volumes of transaction data
- Use of SAST/IAST tools configured with rules for missing authorization on sensitive resource handlers

