CVE-2026-34738: AVideo Video Publishing Workflow Bypass Vulnerability

MODERATE
Advisory Identifier: GHSA-m577-w9j8-ch7j
CVSS 4.3
CWE-285
Published
Advisory Summary

CVE-2026-34738 is a MODERATE (CVSS 4.3) video publishing workflow bypass vulnerability (CWE-285: Improper Authorization) affecting AVideo libraries in the Packagist ecosystem. The issue involves video publishing workflow bypass via unauthorized overridestatus request parameter. Remediation is available in the latest vendor maintenance releases.

CVE-2026-34738 at a Glance

CVE Identifier CVE-2026-34738
GHSA Identifier GHSA-m577-w9j8-ch7j
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification CWE-285: Improper Authorization
Affected Product AVideo
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 4.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-34738

To remediate this vulnerability, upgrade all affected AVideo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

wwbn/avideo fixed: Latest secure release
Upgrade wwbn/avideo to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for wwbn/avideo

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-34738, inspect your project dependencies for AVideo:

inspect dependencies for wwbn/avideo

Analyze the terminal output to locate any version of AVideo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-285: Improper Authorization, where the product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. In AVideo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary AVideo's video processing pipeline accepts an `overrideStatus` request parameter that allows any uploader to set a video's status to any valid state, including "active" (`a`). This bypasses the admin-controlled moderation and draft workflows. The `setStatus()` method validates the status code against a list of known values but does not verify that the caller has permission to set that particular status. As a result, any user with upload permissions can publish videos directly, circumventing content review processes. ## Details At `objects/video.php:1055-1056`, the video object checks for an `overrideStatus` parameter in the request and applies it directly: ```php if (!empty($_REQUEST['overrideStatus'])) { return $this->setStatus($_REQUEST['overrideStatus']); } ``` This code is reached from two entry points: - `objects/videoAddNew.json.php:157` - when adding a new video - `objects/aVideoEncoder.json.php:114` - when processing an encoded video The `setStatus()` method validates that the provided status code is one of the recognized values (`a`, `k`, `i`, `h`, `e`, `x`, `d`, `t`, `u`, `s`, `r`, `f`, `b`, `p`, `c`) but does not perform any authorization check. It does not verify whether the calling user has permission to set a video to the requested status. The relevant status codes include: - `a` - Active (published and publicly visible) - `k` - Draft (pending review) - `i` - Inactive - `e` - Encoding - `x` - Deleted - `u` - Unlisted When an admin configures the platform to require moderation (new videos default to draft/pending status), any uploader can bypass this by including `overrideStatus=a` in their upload request. ## Proof of Concept 1. Assume the AVideo instance has moderation enabled (new videos default to draft status `k`). 2. Upload a video as a regular user, including the `overrideStatus` parameter: ```bash curl -b "PHPSESSID=USER_SESSION" \ -X POST "https://your-avideo-instance.com/objects/videoAddNew.json.php" \ -F "title=Bypassed Moderation" \ -F "description=This video skips the review queue" \ -F "videoLink=https://example.com/video.mp4" \ -F "overrideStatus=a" ``` 3. The video is immediately set to active status and is publicly visible, bypassing the admin moderation workflow. 4. Verify the video is publicly accessible: ```bash curl -s "https://your-avideo-instance.com/video/VIDEO_CLEAN_TITLE" | grep -o "<title>.*</title>" ``` 5. An uploader can also use this to set other statuses: ```bash # Set a video to "unlisted" even if the platform restricts this curl -b "PHPSESSID=USER_SESSION" \ -X POST "https://your-avideo-instance.com/objects/videoAddNew.json.php" \ -F "title=Unlisted Video" \ -F "videoLink=https://example.com/video.mp4" \ -F "overrideStatus=u" ``` ## Impact Any user with upload permissions can bypass content moderation by setting videos directly to active status. This undermines the platform's ability to enforce content policies, review uploads before publication, or maintain a moderation queue. On platforms that rely on moderation for legal compliance (e.g., DMCA, age-gated content), this bypass could have regulatory consequences. The same mechanism also allows uploaders to set arbitrary statuses like "unlisted" or "inactive" on their own videos, bypassing platform-level restrictions on these features. - **CWE-285**: Improper Authorization - **Severity**: Medium ## Recommended Fix Add an authorization check before applying the `overrideStatus` parameter at `objects/video.php:1055`: ```php // objects/video.php:1055 if (!empty($_REQUEST['overrideStatus']) && (User::isAdmin() || Permissions::canAdminVideos())) { return $this->setStatus($_REQUEST['overrideStatus']); } ``` This ensures that only administrators or users with video management permissions can override the video publishing status. Regular uploaders will follow the normal moderation workflow. --- *Found by [aisafe.io](https://aisafe.io)*

CVE-2026-34738 Affected AVideo Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
wwbn/avideo
Packagist
≤ 26.0

References

Frequently Asked Questions

What is CVE-2026-34738?
CVE-2026-34738 is a security vulnerability in AVideo involving Video Publishing Workflow Bypass via Unauthorized overrideStatus Request Parameter under CWE-285: Improper Authorization.
Which AVideo versions are affected?
Affected versions include releases prior to current release patches across affected packages: wwbn/avideo.
What version fixes CVE-2026-34738?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is wwbn/avideo affected?
Yes, wwbn/avideo is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-34738?
CVE-2026-34738 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N.
What CWE is associated with CVE-2026-34738?
CVE-2026-34738 is classified under CWE-285: Improper Authorization (The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.).
How can I check Packagist dependencies for CVE-2026-34738?
Run the dependency tree command: 'inspect dependencies for wwbn/avideo'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-m577-w9j8-ch7j",
  "modified" : "2026-04-01T21:07:24Z",
  "published" : "2026-04-01T21:07:24Z",
  "aliases" : [ "CVE-2026-34738" ],
  "summary" : "AVideo: Video Publishing Workflow Bypass via Unauthorized overrideStatus Request Parameter",
  "details" : "## Summary\n\nAVideo's video processing pipeline accepts an `overrideStatus` request parameter that allows any uploader to set a video's status to any valid state, including \"active\" (`a`). This bypasses the admin-controlled moderation and draft workflows. The `setStatus()` method validates the status code against a list of known values but does not verify that the caller has permission to set that particular status. As a result, any user with upload permissions can publish videos directly, circumventing content review processes.\n\n## Details\n\nAt `objects/video.php:1055-1056`, the video object checks for an `overrideStatus` parameter in the request and applies it directly:\n\n```php\nif (!empty($_REQUEST['overrideStatus'])) {\n    return $this->setStatus($_REQUEST['overrideStatus']);\n}\n```\n\nThis code is reached from two entry points:\n- `objects/videoAddNew.json.php:157` - when adding a new video\n- `objects/aVideoEncoder.json.php:114` - when processing an encoded video\n\nThe `setStatus()` method validates that the provided status code is one of the recognized values (`a`, `k`, `i`, `h`, `e`, `x`, `d`, `t`, `u`, `s`, `r`, `f`, `b`, `p`, `c`) but does not perform any authorization check. It does not verify whether the calling user has permission to set a video to the requested status.\n\nThe relevant status codes include:\n- `a` - Active (published and publicly visible)\n- `k` - Draft (pending review)\n- `i` - Inactive\n- `e` - Encoding\n- `x` - Deleted\n- `u` - Unlisted\n\nWhen an admin configures the platform to require moderation (new videos default to draft/pending status), any uploader can bypass this by including `overrideStatus=a` in their upload request.\n\n## Proof of Concept\n\n1. Assume the AVideo instance has moderation enabled (new videos default to draft status `k`).\n\n2. Upload a video as a regular user, including the `overrideStatus` parameter:\n\n```bash\ncurl -b \"PHPSESSID=USER_SESSION\" \\\n  -X POST \"https://your-avideo-instance.com/objects/videoAddNew.json.php\" \\\n  -F \"title=Bypassed Moderation\" \\\n  -F \"description=This video skips the review queue\" \\\n  -F \"videoLink=https://example.com/video.mp4\" \\\n  -F \"overrideStatus=a\"\n```\n\n3. The video is immediately set to active status and is publicly visible, bypassing the admin moderation workflow.\n\n4. Verify the video is publicly accessible:\n\n```bash\ncurl -s \"https://your-avideo-instance.com/video/VIDEO_CLEAN_TITLE\" | grep -o \"<title>.*</title>\"\n```\n\n5. An uploader can also use this to set other statuses:\n\n```bash\n# Set a video to \"unlisted\" even if the platform restricts this\ncurl -b \"PHPSESSID=USER_SESSION\" \\\n  -X POST \"https://your-avideo-instance.com/objects/videoAddNew.json.php\" \\\n  -F \"title=Unlisted Video\" \\\n  -F \"videoLink=https://example.com/video.mp4\" \\\n  -F \"overrideStatus=u\"\n```\n\n## Impact\n\nAny user with upload permissions can bypass content moderation by setting videos directly to active status. This undermines the platform's ability to enforce content policies, review uploads before publication, or maintain a moderation queue. On platforms that rely on moderation for legal compliance (e.g., DMCA, age-gated content), this bypass could have regulatory consequences. The same mechanism also allows uploaders to set arbitrary statuses like \"unlisted\" or \"inactive\" on their own videos, bypassing platform-level restrictions on these features.\n\n- **CWE-285**: Improper Authorization\n- **Severity**: Medium\n\n## Recommended Fix\n\nAdd an authorization check before applying the `overrideStatus` parameter at `objects/video.php:1055`:\n\n```php\n// objects/video.php:1055\nif (!empty($_REQUEST['overrideStatus']) && (User::isAdmin() || Permissions::canAdminVideos())) {\n    return $this->setStatus($_REQUEST['overrideStatus']);\n}\n```\n\nThis ensures that only administrators or users with video management permissions can override the video publishing status. Regular uploaders will follow the normal moderation workflow.\n\n---\n*Found by [aisafe.io](https://aisafe.io)*",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "wwbn/avideo"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "26.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/WWBN/AVideo/security/advisories/GHSA-m577-w9j8-ch7j"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34738"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/WWBN/AVideo/commit/34f0237e2449d2e564a69fe3c5c71c830f5d11fd"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/WWBN/AVideo"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-285" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-01T21:07:24Z",
    "nvd_published_at" : "2026-03-31T21:16:32Z"
  }
}