How severe is GHSA-rhvc-x32h-5526?

No CVSS score has been assigned to GHSA-rhvc-x32h-5526 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rhvc-x32h-5526?

GHSA-rhvc-x32h-5526 affects the following packages: droppy (npm). Ecosystems affected: npm.

How do I fix GHSA-rhvc-x32h-5526?

Update droppy to 3.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rhvc-x32h-5526 is resolved across your whole dependency graph.

How do I detect GHSA-rhvc-x32h-5526 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for droppy. 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-rhvc-x32h-5526 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-rhvc-x32h-5526?

O3 pinpoints whether GHSA-rhvc-x32h-5526 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-rhvc-x32h-5526 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rhvc-x32h-5526 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.

What type of vulnerability is GHSA-rhvc-x32h-5526?

GHSA-rhvc-x32h-5526 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rhvc-x32h-5526 published, and has it been updated?

GHSA-rhvc-x32h-5526 was published on February 18, 2019 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-rhvc-x32h-5526

GHSA-rhvc-x32h-5526 is a Cross-Site Request Forgery (CSRF) vulnerability in droppy. O3 Security confirms whether GHSA-rhvc-x32h-5526 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

No CSRF Validation in droppy

Also known asCVE-2016-10529

Published

Feb 18, 2019

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

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.

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

droppynpm

263downloads / week

Description

Affected versions of droppy are vulnerable to cross-site socket forgery. The package does not perform verification for cross-domain websocket requests, and as a result, an attacker can create a web page that opens up a websocket connection on behalf of the user visiting the page. The attacker can then perform any action that the target user could, including adding a new admin account under their control, or deleting others.

Recommendation

Update to version 3.5.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`droppy`	all versions	3.5.0

Detection & mitigation playbook

Open-source dependency

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

Frequently Asked Questions

Affected versions of `droppy` are vulnerable to cross-site socket forgery. The package does not perform verification for cross-domain websocket requests, and as a result, an attacker can create a web page that opens up a websocket connection on behalf of the user visiting the page. The attacker can then perform any action that the target user could, including adding a new admin account under their control, or deleting others. ## Recommendation Update to version 3.5.0 or later.

O3 Security · Impact-Aware SCA

Is GHSA-rhvc-x32h-5526 in your dependencies?

O3 detects GHSA-rhvc-x32h-5526 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