CVE-2023-30860 — avideo
HIGHCVE-2023-30860 is a high-severity (CVSS 8) Cross-site Scripting (XSS) vulnerability in wwbn/avideo. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for wwbn/avideo — see the affected versions and patch details below.
WWBN/AVideo stored XSS vulnerability leads to takeover of any user's account, including admin's account
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-30860.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
wwbn/avideoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
In AVideo, a normal user can make a Meeting Schedule where the user can invite another user in that Meeting, but I found out that it did not properly sanitize the malicious characters when creating a Meeting Room. This leads the attacker to put malicious scripts.
Impact:
Since any USER including the ADMIN can see the meeting room that was created by the attacker this can lead to cookie hijacking and takeover of any accounts without user interaction.
Step to Reproduce:
- As normal USER go to Meet -> Schedule
https://demo.avideo.com/plugin/Meet/
- In "Meet topic" field put XSS payload
Example: "><img src=x onerror=alert('Pawned+by+Gonz')>
-
Then click Save
-
Now as ADMIN go to Meet -> Schedule -> Upcoming
https://demo.avideo.com/plugin/Meet/
- Then the XSS payload that normal USER created will be executed
Video POC: https://youtu.be/Nke0Bmv5F-o
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | wwbn/avideo | all versions | 12.4composer require wwbn/avideo:^12.4 |
Affected Products
avideowwbnResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wwbn/avideo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update wwbn/avideo to 12.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-30860 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2023-30860 in your dependencies?
Find it across Packagist, including transitive dependencies.