{"answers":{"affected":"2 open source packages ship an affected version, including wwbn/avideo. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34362 exists.","fix":"No fix has been published for CVE-2026-34362 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34362 is a medium-severity vulnerability in Wwbn Avideo, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34362 and fix it if it is affected.\n\nWhat it is: CVE-2026-34362 is a medium-severity vulnerability in Wwbn Avideo, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34362 exists.\n\nAffected packages and fixed versions:\n- wwbn/avideo (Packagist): affected all versions up to 26.0; no fix listed\n- wwbn/avideo (Packagist): affected all versions up to 26.0; no fix listed\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-34362/ (Markdown: https://insights.sbomify.com/CVE-2026-34362/index.md)","id":"CVE-2026-34362","markdown":"https://insights.sbomify.com/CVE-2026-34362/index.md","name":"CVE-2026-34362","record":{"aliases":["GHSA-2mg4-pfgx-64cf"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Video platform","requires_auth":"low_privilege","summary":"Attackers can use expired WebSocket tokens to permanently access real-time user data and maintain access after account deletion due to disabled timeout validation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"avideo","vendor":"wwbn"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"WWBN AVideo is an open source video platform. In versions up to and including 26.0, the `verifyTokenSocket()` function in `plugin/YPTSocket/functions.php` has its token timeout validation commented out, causing WebSocket tokens to never expire despite being generated with a 12-hour timeout. This allows captured or legitimately obtained tokens to provide permanent WebSocket access, even after user accounts are deleted, banned, or demoted from admin. Admin tokens grant access to real-time connection data for all online users including IP addresses, browser info, and page locations. Commit 5d5237121bf82c24e9e0fdd5bc1699f1157783c5 fixes the issue.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"AVideo's WebSocket Token Never Expires Due to Commented-Out Timeout Validation in verifyTokenSocket()","id":"CVE-2026-34362","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"wwbn:avideo","products":["wwbn:avideo"],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Parse Server: LiveQuery protected field leak via shared mutable state across concurrent subscribers","id":"CVE-2026-34363"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["26.0"],"package":"wwbn/avideo","purl":null,"source":"GHSA-2mg4-pfgx-64cf"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["26.0"],"package":"wwbn/avideo","purl":"pkg:composer/wwbn/avideo","source":"GHSA-2mg4-pfgx-64cf"}],"prev":{"headline":"HAPI FHIR: Unauthenticated SSRF via /loadIG Chains with startsWith() Credential Leak for Authentication Token Theft","id":"CVE-2026-34361"},"products":["AVideo"],"published":"2026-03-27","related":[{"cvss_score":10,"headline":"WWBN AVideo YPTSocket WebSocket Broadcast Relay Leads to Unauthenticated Cross-User JavaScript Execution via Client-Side eval() Sinks","id":"CVE-2026-40911","kev_date_added":null,"published":"2026-04-21"},{"cvss_score":10,"headline":"AVideo Multi-Chain Attack: Unauthenticated Remote Code Execution via Clone Key Disclosure, Database Dump, and Command Injection","id":"CVE-2026-33478","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":9.9,"headline":"Command injection in AVideo","id":"CVE-2022-30534","kev_date_added":null,"published":"2022-08-22"},{"cvss_score":9.9,"headline":"Path traversal in AVideo","id":"CVE-2022-30547","kev_date_added":null,"published":"2022-08-22"},{"cvss_score":9.9,"headline":"Command injection in AVideo","id":"CVE-2022-32572","kev_date_added":null,"published":"2022-08-22"},{"cvss_score":9.8,"headline":"AVideo has an Unauthenticated SQL Injection via `doNotShowCats` Parameter (Backslash Escape Bypass)","id":"CVE-2026-33352","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":9.8,"headline":"WWBN AVideo: Unauthenticated SQL Injection via JSON Request Bypass in objects/videos.json.php","id":"CVE-2026-28501","kev_date_added":null,"published":"2026-03-06"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-31","vendors":["WWBN"]},"summary":"Attackers can use expired WebSocket tokens to permanently access real-time user data and maintain access after account deletion due to disabled timeout validation.","url":"https://insights.sbomify.com/CVE-2026-34362/"}