No CSRF Validation in droppy

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.

Recommendation

Update the droppy package to the latest compatible version. Followings are version details:

• Affected version(s): < 3.5.0
• Patched version(s): 3.5.0

References

• GHSA-rhvc-x32h-5526
• www.npmjs.com
• CVE-2016-10529
• CWE-352
• CAPEC-310
• OWASP 2021-A1
• OWASP 2021-A6

Related Issues

• XSS due to lack of CSRF validation for replying/publishing - CVE-2020-15156
• Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints - @payloadcms/storage-r2 - CVE-2026-34750
• Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints - @payloadcms/storage-gcs - CVE-2026-34750
• Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints - @payloadcms/storage-azure - CVE-2026-34750

You might also like:

CSRF, XXE, and 12 Other Security Acronyms Explained

How to Secure your NodeJs Express Javascript Application - part 1

Update Cheat Sheet for Developers

Tags:

npm

droppy