HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 56341 avideo unauthenticated access to payment log
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High · CVSS 7.5CVE-2026-56341GHSA-WPRJ-9CVC-5W37

AVideo: Unauthenticated Access to Payment Log DataTables Endpoints Exposes Transaction Data, PayPal Tokens, and User Financial RecordsCVE-2026-56341

Answer in brief

CVE-2026-56341 records a High severity (CVSS 7.5) vulnerability in AVideo: Unauthenticated Access to Payment Log DataTables Endpoints Exposes Transaction Data, PayPal Tokens, and User Financial Records. The current sources do not mark it as known exploited. The current feed maps wwbn/avideo (composer), wwbn/avideo (packagist). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Mar 29, 2026Updated Sep 10, 2026Source checked Oct 25, 2026First seen by HOL Jun 20, 2026Material review Sep 10, 2026
Upstream Advisory

Key facts

Risk
High · CVSS 7.5
Exploitation
Not marked as known exploited
Affected software
2 mapped packages or products
Fix availability
Not reported

Why this deserves its current priority

CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps wwbn/avideo (composer), wwbn/avideo (packagist). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
wwbn/avideocomposer<=26.0Not reported
wwbn/avideopackagist>=0Not reported

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for wwbn/avideo, wwbn/avideo.
  2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

  1. Published upstream

    Mar 29, 2026

    Evidence: source:ghsa:source_dates:source-dates:record
  2. Source modified

    Sep 10, 2026

    Evidence: source:ghsa:source_dates:source-dates:record
  3. First seen by HOL

    Jun 20, 2026

Sources and claim methodology

  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • NVD vulnerability recordnvd.nist.gov
  • Source referencevulncheck.com
  • GitHub security advisorygithub.com
Upstream source description

## Summary Multiple payment plugin `list.json.php` endpoints lack authentication and authorization checks, allowing unauthenticated attackers to retrieve all payment transaction records including PayPal billing agreement IDs, Express Checkout tokens, Authorize.Net webhook payloads with transaction details, and Bitcoin payment records. This is the same class of vulnerability fixed in the Scheduler plugin (GHSA-j724-5c6c-68g5 / commit 83390ab1f) but the fix was not applied to the remaining 21 affected endpoints. ## Details The AVideo ObjectYPT admin CRUD pattern generates four endpoints per database table: `add.json.php`, `delete.json.php`, `list.json.php`, and an `index.php` page. In the payment plugins, `add.json.php` and `delete.json.php` correctly check `User::isAdmin()` before proceeding, but the `list.json.php` endpoints have no authorization check whatsoever. **PayPalYPT_log list endpoint** (`plugin/PayPalYPT/View/PayPalYPT_log/list.json.php:1-10`): ```php <?php require_once '../../../../videos/configuration.php'; require_once $global['systemRootPath'] . 'plugin/PayPalYPT/Objects/PayPalYPT_log.php'; header('Content-Type: application/json'); $rows = PayPalYPT_log::getAll(); $total = PayPalYPT_log::getTotal(); ?> {"data": <?php echo json_encode($rows); ?>, ...} ``` No `User::isAdmin()` check. The `getAll()` method (inherited from `ObjectYPT`) executes `SELECT * FROM PayPalYPT_log` returning all records. **Contrast with the sibling add endpoint** (`plugin/PayPalYPT/View/PayPalYPT_log/add.json.php:13-16`): ```php if (!User::isAdmin()) { $obj->msg = "You can't do this"; die(json_encode($obj)); } ``` The `configuration.php` bootstrap file performs no global authentication gating — it initializes the application framework but does not enforce auth. No `.htaccess` rules restrict access to plugin View directories. **Data model** (`plugin/PayPalYPT/Objects/PayPalYPT_log.php`): Each record contains `agreement_id`, `users_id`, `json` (full PayPal API response), `recurring_payment_id`, `value` (payment amount), and `token` (PayPal Express Checkout token). The identical pattern exists in: - `plugin/AuthorizeNet/View/Anet_webhook_log/list.json.php` — full Authorize.Net webhook payloads - `plugin/BTCPayments/View/Btc_payments/list.json.php` — Bitcoin transaction identifiers and amounts This was the exact same vulnerability class patched in commit 83390ab1f for the Scheduler plugin (GHSA-j724-5c6c-68g5), but the fix was only applied to the 3 Scheduler endpoints. A total of 21 `list.json.php` endpoints across the codebase remain unprotected. ## PoC **Step 1 — Dump PayPal transaction logs (unauthenticated):** ```bash curl -s 'https://target.com/plugin/PayPalYPT/View/PayPalYPT_log/list.json.php' ``` Returns all PayPal transaction records including agreement IDs, tokens, payment amounts, user IDs, and full PayPal API JSON responses. **Step 2 — Dump Authorize.Net webhook logs (unauthenticated):** ```bash curl -s 'https://target.com/plugin/AuthorizeNet/View/Anet_webhook_log/list.json.php' ``` Returns all Authorize.Net webhook payloads including transaction IDs, event types, and payment details. **Step 3 — Dump Bitcoin payment records (unauthenticated):** ```bash curl -s 'https://target.com/plugin/BTCPayments/View/Btc_payments/list.json.php' ``` Returns all Bitcoin transaction identifiers, BTC amounts, and store identifiers. **Step 4 — Confirm sibling endpoints ARE protected:** ```bash curl -s -X POST 'https://target.com/plugin/PayPalYPT/View/PayPalYPT_log/add.json.php' # Returns: {"error":true,"msg":"You can't do this"} ``` ## Impact - **Financial data exposure:** Unauthenticated attackers can retrieve all payment transaction records across PayPal, Authorize.Net, and Bitcoin payment providers. - **Token leakage:** PayPal Express Checkout tokens and billing agreement IDs are exposed, potentially enabling payment manipulation or account correlation. - **PII leakage:** Transaction records contain user ID mappings, payment amounts, and full API responses that may include payer email addresses and names. - **Broad scope:** 21 total `list.json.php` endpoints lack auth, also exposing live streaming server infrastructure (`Live_servers`), user connection data, meeting participation logs, and AI transcription responses. - **Zero interaction required:** No authentication, no user interaction — a single GET request dumps the entire table. ## Recommended Fix Add `User::isAdmin()` checks to all unprotected `list.json.php` endpoints, matching the pattern used in the Scheduler fix (commit 83390ab1f). For each affected file, add immediately after the `require_once` and `header()` lines: ```php if (!User::isAdmin()) { $obj = new stdClass(); $obj->error = true; $obj->msg = "You can't do this"; die(json_encode($obj)); } ``` The full list of files requiring this fix: 1. `plugin/PayPalYPT/View/PayPalYPT_log/list.json.php` 2. `plugin/AuthorizeNet/View/Anet_webhook_log/list.json.php` 3. `plugin/BTCPayments/View/Btc_payments/list.json.php` 4. `plugin/AI/View/Ai_responses/list.json.php` 5. `plugin/AI/View/Ai_metatags_responses/list.json.php` 6. `plugin/AI/View/Ai_transcribe_responses/list.json.php` 7. `plugin/Live/view/Live_servers/list.json.php` 8. `plugin/Live/view/Live_schedule/list.json.php` 9. `plugin/Live/view/Live_restreams_logs/list.json.php` 10. `plugin/SocialMediaPublisher/View/Publisher_schedule/list.json.php` 11. `plugin/SocialMediaPublisher/View/Publisher_social_medias/list.json.php` 12. `plugin/Meet/View/Meet_join_log/list.json.php` 13. `plugin/Meet/View/Meet_schedule_has_users_groups/list.json.php` 14. `plugin/PlayLists/View/Playlists_schedules/list.json.php` 15. `plugin/UserConnections/View/Users_connections/list.json.php` 16. `plugin/UserNotifications/View/User_notifications/list.json.php` 17. `plugin/VideosStatistics/View/Statistics/list.json.php` 18. `plugin/VideoTags/View/Tags_subscriptions/list.json.php` 19. `plugin/CustomizeUser/View/Categories_has_users_groups/list.json.php` 20. `plugin/CustomizeUser/View/Users_extra_info/list.json.php` 21. `plugin/ImageGallery/list.json.php`

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • WordPress SureDash plugin <= 1.12.2 - Broken Access Control vulnerabilityAlso CWE-862
  • WordPress UPI QR Code Payment Gateway for WooCommerce plugin <= 1.6.3 - Broken Access Control vulnerabilityAlso CWE-862
  • WordPress WpEvently plugin <= 5.7.8 - Broken Access Control vulnerabilityAlso CWE-862
  • WordPress WP Social Feed Gallery plugin <= 5.0.13 - Broken Access Control vulnerabilityAlso CWE-862
  • FaveoSuite Faveo Helpdesk UnAuthController.php UnAuthController.resolve authorizationAlso CWE-862
  • DaybydayCRM through 2.2.1 Missing Authorization via ProjectsController updateAssignAlso CWE-862

Record context

Vulnerability class
Missing Auth
EPSS
Not reported
CWE IDs
CWE-862, CWE-200
Source
GitHub Security Advisories
Source checked
Oct 25, 2026
References
7 linked sources
Open source record