WWBN/AVideo stored XSS vulnerability leads to takeover of any user's account, including admin's account

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.0 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

EPSS

• CVE-2023-30860: 0.71% estimated exploitation activity in the next 30 days; percentile 53.42 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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: 1. As normal USER go to Meet - Schedule https://demo.avideo.com/plugin/Meet/ 2. In "Meet topic" field put XSS payload Example: "<img src=x onerror=alert('Pawned+by+Gonz') 3. Then click Save 4. Now as ADMIN go to Meet - Schedule - Upcoming https://demo.avideo.com/plugin/Meet/ 5. Then the XSS payload that normal USER created will be executed Video POC: https://youtu.be/Nke0Bmv5F-o

Published by the source

1 May 2023, 22:30 UTC

Last modified by the source

7 Nov 2023, 05:06 UTC

Source last checked

26 Oct 2026, 14:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xr9h-p2rc-rpqm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-30860

Advisory: WWBN/AVideo stored XSS vulnerability leads to takeover of any user's account, including admin's account
IDs: CVE-2023-30860, GHSA-xr9h-p2rc-rpqm
Record: https://patchnext.com/advisories/cve-2023-30860 (revision 1, source checked 26 Oct 2026, 14:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: wwbn/avideo 12.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist wwbn/avideo: affected < 12.4; fixed in 12.4

## Suggested inspection (read-only)
- Packagist wwbn/avideo: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on wwbn/avideo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xr9h-p2rc-rpqm (GitHub-reviewed advisory GHSA-xr9h-p2rc-rpqm lists affected ranges: Packagist wwbn/avideo >=0 <12.4)

Commands are suggestions: review each one before running it.