How severe is GHSA-xr9h-p2rc-rpqm?

GHSA-xr9h-p2rc-rpqm has a CVSS score of 8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-xr9h-p2rc-rpqm?

GHSA-xr9h-p2rc-rpqm affects the following packages: wwbn/avideo (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-xr9h-p2rc-rpqm?

Update wwbn/avideo to 12.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xr9h-p2rc-rpqm is resolved across your whole dependency graph.

How do I detect GHSA-xr9h-p2rc-rpqm in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wwbn/avideo. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-xr9h-p2rc-rpqm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-xr9h-p2rc-rpqm?

O3 pinpoints whether GHSA-xr9h-p2rc-rpqm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-xr9h-p2rc-rpqm actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-xr9h-p2rc-rpqm, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-xr9h-p2rc-rpqm?

GHSA-xr9h-p2rc-rpqm has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 49th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-xr9h-p2rc-rpqm?

GHSA-xr9h-p2rc-rpqm is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-xr9h-p2rc-rpqm published, and has it been updated?

GHSA-xr9h-p2rc-rpqm was published on May 1, 2023 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-xr9h-p2rc-rpqm

HIGH

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

Also known asCVE-2023-30860

Published

May 1, 2023

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk49th percentile-3.45%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐘wwbn/avideo

Real-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

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`wwbn/avideo`	all versions	12.4

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

WWBN AVideo is an open source video platform. In AVideo prior to version…

github.comNVDMay 2023

WWBN AVideo is an open source video platform. In AVideo prior to version…

youtu.beNVDMay 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wwbn/avideo. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update wwbn/avideo to 12.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xr9h-p2rc-rpqm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-xr9h-p2rc-rpqm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-xr9h-p2rc-rpqm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 E

O3 Security · Impact-Aware SCA

Is GHSA-xr9h-p2rc-rpqm in your dependencies?

O3 detects GHSA-xr9h-p2rc-rpqm across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works