How severe is GHSA-2fch-hv74-fgw9?

No CVSS score has been assigned to GHSA-2fch-hv74-fgw9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2fch-hv74-fgw9?

GHSA-2fch-hv74-fgw9 affects the following packages: wwbn/avideo (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-2fch-hv74-fgw9?

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

How do I detect GHSA-2fch-hv74-fgw9 in my Packagist dependencies?

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.

How do I mitigate GHSA-2fch-hv74-fgw9 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-2fch-hv74-fgw9?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2fch-hv74-fgw9 can be triaged on real exposure rather than presence alone.

Is GHSA-2fch-hv74-fgw9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2fch-hv74-fgw9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2fch-hv74-fgw9 published, and has it been updated?

GHSA-2fch-hv74-fgw9 was published on April 26, 2023 and was last updated on December 3, 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

Not in CISA KEV

GHSA-2fch-hv74-fgw9 — wwbn/avideo

GHSA-2fch-hv74-fgw9 is a security vulnerability in wwbn/avideo. A fix is available for wwbn/avideo — see the affected versions and patch details below.

Cross site scripting (XSS) in wwbn/avideo

Published

Apr 26, 2023

Updated

Dec 3, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 3, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

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

Description:

While making an account in demo.avideo.com I found a parameter "?success=" which did not sanitize any symbol character properly which leads to XSS attack.

Impact:

Since there's an Admin account on demo.avideo.com attacker can use this attack to Takeover the admin's account

Step to Reproduce:

Click the link below

https://demo.avideo.com/user?success="><img src=x onerror=alert(document.cookie)>

Then XSS will be executed

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`wwbn/avideo`	all versions	12.4`composer require wwbn/avideo:^12.4`

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, 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 GHSA-2fch-hv74-fgw9 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2fch-hv74-fgw9 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-2fch-hv74-fgw9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Description: While making an account in demo.avideo.com I found a parameter "?success=" which did not sanitize any symbol character properly which leads to XSS attack. Impact: Since there's an Admin account on demo.avideo.com attacker can use this attack to Takeover the admin's account Step to Reproduce: 1. Click the link below [https://demo.avideo.com/user?success="><img](https://demo.avideo.com/user?success=%22%3E%3Cimg) src=x onerror=alert(document.cookie)> 2. Then XSS will be executed

O3 Security · Impact-Aware SCA

Is GHSA-2fch-hv74-fgw9 in your dependencies?

O3 Security finds GHSA-2fch-hv74-fgw9 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works