CVE-2026-56341
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAVideo through version 26.0 contains multiple unauthenticated list.json.php endpoints in payment plugins lacking authorization checks, exposing PayPal tokens, Authorize.Net webhooks, and Bitcoin transaction records. Unauthenticated attackers can retrieve all payment transaction data including agreement IDs, user financial records, and API responses via direct GET requests to vulnerable endpoints.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAVideo platform versions up to 26.0 contain multiple unauthenticated list.json.php endpoints in payment plugins that lack proper authorization checks. These vulnerable endpoints expose sensitive payment data including PayPal tokens, Authorize.Net webhook credentials, Bitcoin transaction records, user financial information, and API responses to any unauthenticated attacker via direct HTTP GET requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm AVideo platform installationIdentify if your web server hosts an AVideo (formerly YouPHPTube) platform instance. Check for AVideo-specific directories, login pages, or the presence of avideo directory structure in your web root.Affected if Your environment runs AVideo software
-
Check installed AVideo versionLocate the version file or admin panel that displays the AVideo version number. Compare it to the affected range: versions up to and including 26.0 are vulnerable.Affected if Your AVideo version is 26.0 or lower
-
Identify payment pluginsExamine your AVideo installation for payment-related plugins in the plugin directory. Look for directories or files containing names like paypal, authorize, bitcoin, payment, stripe, or similar payment processor names.Affected if You have any payment plugins installed
-
Test list.json.php endpoint accessibilityUsing a web browser or curl tool, attempt direct HTTP GET requests to list.json.php files within payment plugin directories without providing any authentication credentials. Example: visit yoursite.com/plugin/paypal/list.json.phpAffected if The endpoint returns data (payment tokens, transaction records, user financial information) without requiring login
-
Verify sensitive data exposureExamine responses from unauthenticated list.json.php endpoints for presence of PayPal tokens, Authorize.Net credentials, Bitcoin transaction data, API keys, or user financial information in the JSON output.Affected if The response contains sensitive payment credentials or financial data visible to unauthenticated users
Your environment is affected if you run AVideo version 26.0 or lower with any payment plugins installed, and the list.json.php endpoints in those plugins are accessible without authentication and expose payment credentials or financial data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImplement role-based access control and authentication checks on all list.json.php endpoints in payment plugins to ensure only authorized users can access transaction data. Rotate any exposed credentials (PayPal tokens, API keys) immediately and audit logs for unauthorized access attempts.
Latest stable AVideo release beyond version 26.0 (check github.com/AVideo/AVideo for current stable release)
- 1. Identify all AVideo installations in your environment running version 26.0 or earlier
- 2. Check the official AVideo repository (github.com) for security releases or patches addressing the unauthenticated list.json.php endpoints in payment plugins
- 3. If a security release is available, download and apply it following the standard AVideo upgrade procedure
- 4. If no official patch is available, implement temporary mitigations: configure web server (Apache/Nginx) to require authentication for all list.json.php endpoints in plugin directories, or temporarily disable the affected payment plugins until a fix is released
- 5. After applying the fix, verify that all payment plugin endpoints now require authentication
- 6. Audit existing access logs for any unauthorized attempts to access the vulnerable endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56341 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56341 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data