{"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-33500 exists.","fix":"No fix has been published for CVE-2026-33500 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33500 is a medium-severity cross-site scripting vulnerability in Wwbn Avideo, published on 23 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-33500 and fix it if it is affected.\n\nWhat it is: CVE-2026-33500 is a medium-severity cross-site scripting vulnerability in Wwbn Avideo, published on 23 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33500 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-33500/ (Markdown: https://insights.sbomify.com/CVE-2026-33500/index.md)","id":"CVE-2026-33500","markdown":"https://insights.sbomify.com/CVE-2026-33500/index.md","name":"CVE-2026-33500","record":{"aliases":["GHSA-72h5-39r7-r26j"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Video platform","requires_auth":"low_privilege","summary":"Attackers can inject stored XSS via markdown links in comments due to sanitization bypass, potentially leading to session hijacking or malicious script execution.","user_interaction":"required","vuln_class":"xss"},"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:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"WWBN AVideo is an open source video platform. In versions up to and including 26.0, the fix for CVE-2026-27568 (GHSA-rcqw-6466-3mv7) introduced a custom `ParsedownSafeWithLinks` class that sanitizes raw HTML `\u003ca\u003e` and `\u003cimg\u003e` tags in comments, but explicitly disables Parsedown's `safeMode`. This creates a bypass: markdown link syntax `[text](javascript:alert(1))` is processed by Parsedown's `inlineLink()` method, which does not go through the custom `sanitizeATag()` sanitization (that only handles raw HTML tags). With `safeMode` disabled, Parsedown's built-in `javascript:` URI filtering (`sanitiseElement()`/`filterUnsafeUrlInAttribute()`) is also inactive. An attacker can inject stored XSS via comment markdown links. Commit 3ae02fa240939dbefc5949d64f05790fd25d728d contains a patch.","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 Vulnerable to Stored XSS via Markdown `javascript:` URI Bypasses ParsedownSafeWithLinks Sanitization","id":"CVE-2026-33500","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":"wwbn:avideo","products":["wwbn:avideo"],"type":"xss","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"AVideo has Unauthenticated Information Disclosure of User Group Permission Mappings via Permissions Plugin","id":"CVE-2026-33501"},"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["26.0"],"package":"wwbn/avideo","purl":null,"source":"GHSA-72h5-39r7-r26j"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["26.0"],"package":"wwbn/avideo","purl":"pkg:composer/wwbn/avideo","source":"GHSA-72h5-39r7-r26j"}],"prev":{"headline":"AVideo has Reflected XSS via unlockPassword Parameter in forbiddenPage.php and warningPage.php","id":"CVE-2026-33499"},"products":["AVideo"],"published":"2026-03-23","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-24","vendors":["WWBN"]},"summary":"Attackers can inject stored XSS via markdown links in comments due to sanitization bypass, potentially leading to session hijacking or malicious script execution.","url":"https://insights.sbomify.com/CVE-2026-33500/"}