How severe is GHSA-xwqw-rf2q-xmhf?

No CVSS score has been assigned to GHSA-xwqw-rf2q-xmhf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xwqw-rf2q-xmhf?

GHSA-xwqw-rf2q-xmhf affects the following packages: buefy (npm). Ecosystems affected: npm.

How do I fix GHSA-xwqw-rf2q-xmhf?

Update buefy to 0.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xwqw-rf2q-xmhf is resolved across your whole dependency graph.

How do I detect GHSA-xwqw-rf2q-xmhf in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for buefy. 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-xwqw-rf2q-xmhf 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-xwqw-rf2q-xmhf?

O3 pinpoints whether GHSA-xwqw-rf2q-xmhf 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-xwqw-rf2q-xmhf actively exploited in the wild?

No public exploit code has been indexed for GHSA-xwqw-rf2q-xmhf 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-xwqw-rf2q-xmhf published, and has it been updated?

GHSA-xwqw-rf2q-xmhf was published on September 1, 2020 and was last updated on September 24, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-xwqw-rf2q-xmhf: Cross-Site Scripting…

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

168other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

buefynpm

45Kdownloads / week

Description

Versions of buefy prior to 0.7.2 are vulnerable to Cross-Site Scripting, allowing attackers to manipulate the DOM and execute remote code. The autocomplete list renders user input as HTML without encoding.

Recommendation

Upgrade to version 0.7.2 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`buefy`	all versions	0.7.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for buefy. 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 buefy to 0.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xwqw-rf2q-xmhf 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-xwqw-rf2q-xmhf 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-xwqw-rf2q-xmhf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of buefy prior to 0.7.2 are vulnerable to Cross-Site Scripting, allowing attackers to manipulate the DOM and execute remote code. The autocomplete list renders user input as HTML without encoding. ## Recommendation Upgrade to version 0.7.2 or later.

O3 Security · Impact-Aware SCA

Is GHSA-xwqw-rf2q-xmhf in your dependencies?

O3 detects GHSA-xwqw-rf2q-xmhf across npm 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

GHSA-xwqw-rf2q-xmhf