{"answers":{"affected":"2 open source packages ship an affected version, including wwbn/avideo.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33684 exists.","fix":"Upgrade wwbn/avideo to 29.0 or later.","what":"CVE-2026-33684 is a medium-severity vulnerability in WWBN AVideo, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33684 and fix it if it is affected.\n\nWhat it is: CVE-2026-33684 is a medium-severity vulnerability in WWBN AVideo, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33684 exists.\n\nAffected packages and fixed versions:\n- wwbn/avideo (Packagist): affected all versions; fixed in 29.0\n- wwbn/avideo (Packagist): affected all versions; fixed in 29.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33684/ (Markdown: https://insights.sbomify.com/CVE-2026-33684/index.md)","id":"CVE-2026-33684","markdown":"https://insights.sbomify.com/CVE-2026-33684/index.md","name":"CVE-2026-33684","record":{"aliases":["GHSA-8j8m-p79x-g4jm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Video platform","requires_auth":"none","summary":"Attackers can self-grant elevated permissions like upload and streaming during registration by bypassing API authentication checks in AVideo.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"WWBN AVideo is an open source video platform. Prior to version 29.0, Privilege Escalation is possible through unguarded permission parameters in signUp API, which allows any user who can solve a CAPTCHA to self-grant elevated permissions during account registration. The set_api_signUp method in the API plugin accepts emailVerified, canUpload, canStream, and canCreateMeet parameters from user-supplied input and applies them to newly created accounts without verifying that the request was authenticated with a valid APISecret. By self-granting account attributes, attackers can mark their own accounts as email-verified without owning the address (bypassing email-gated functionality) and award themselves upload, streaming, and meeting-creation permissions, circumventing administrator access controls that intentionally restrict these capabilities for new users. This issue has been fixed in version 29.0","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"AVideo's Privilege Escalation via Unguarded Permission Parameters in signUp API Allows Self-Granting Upload/Stream/Meet Permissions","id":"CVE-2026-33684","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"AVideo Allows Unauthenticated Access to AD_Server reports.json.php that Exposes Ad Campaign Analytics and User Data","id":"CVE-2026-33685"},"packages":[{"ecosystem":"Packagist","fixed":["29.0"],"introduced":["0"],"last_affected":[],"package":"wwbn/avideo","purl":null,"source":"GHSA-8j8m-p79x-g4jm"},{"ecosystem":"Packagist","fixed":["29.0"],"introduced":["0"],"last_affected":[],"package":"wwbn/avideo","purl":"pkg:composer/wwbn/avideo","source":"GHSA-8j8m-p79x-g4jm"}],"prev":{"headline":"AVideo vulnerable to Stored XSS via html_entity_decode() Reversing xss_esc() Sanitization in Channel About Field","id":"CVE-2026-33683"},"products":["AVideo"],"published":"2026-07-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-16","vendors":["WWBN"]},"summary":"Attackers can self-grant elevated permissions like upload and streaming during registration by bypassing API authentication checks in AVideo.","url":"https://insights.sbomify.com/CVE-2026-33684/"}