Payment log disclosure via unguarded list endpoints
Published Jun 20, 2026 · Updated Jun 20, 2026
Missing authorization in AVideo 26.0 and earlier allows remote attackers to read payment transaction logs via direct HTTP GET requests. Each payment plugin's list.json.php calls getAll() and serializes every table row without checking User::isAdmin(). Exposure requires an affected payment plugin to be installed; returned records include user IDs, amounts, provider payloads, and PayPal tokens.
Summary
What happened
Missing authorization in AVideo 26.0 and earlier allows remote attackers to read payment transaction logs via direct HTTP GET requests. Each payment plugin's list.json.php calls getAll() and serializes every table row without checking User::isAdmin(). Exposure requires an affected payment plugin to be installed; returned records include user IDs, amounts, provider payloads, and PayPal tokens.
The record
- CVE
- CVE-2026-56341
- Published
- Jun 20, 2026
- Updated
- Jun 20, 2026
- Vendor
- World Wide Broadcast Network
- Product
- AVideo
- Classifications
- CWE-862, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 20, 2026CVE publishedPublication date reported by the CVE source.
- Jun 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=26.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GHSA-wprj-9cvc-5w37 unauthenticated payment-log disclosure PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo