CVE-2024-22416criticalCWE-352

CVE-2024-22416: critical vulnerability in pyload

Cross-Site Request Forgery on any API call in pyLoad may lead to admin privilege escalation

Published · Updated

Follow this CVE+ Monitor pyload+ Monitor pyload-ng

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

28Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 9.7epss 0.9%
pyLoad is a free and open-source Download Manager written in pure Python. The `pyload` API allows any API call to be made using GET requests. Since the session cookie is not set to `SameSite: strict`, this opens the library up to severe attack possibilities via a Cross-Site Request Forgery (CSRF) attack. As a result any API call can be made via a CSRF attack by an unauthenticated user. This issue has been addressed in release `0.5.0b3.dev78`. All users are advised to upgrade.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Affected products
pyload · pyload
Related CVEs — pyload

In the same product, most dangerous first.

CVE-2024-21644HIGHpyLoad unauthenticated flask configuration leakageEPSS 42.4%CVE-2024-21645MEDIUMpyLoad Log InjectionEPSS 24.7%CVE-2025-54802CRITICALpyLoad CNL Blueprint is vulnerable to Path Traversal through `dlc_path` leading to Remote Code Execution (RCE)EPSS 1.4%CVE-2024-32880CRITICALpyLoad allows upload to arbitrary folder lead to RCEEPSS 1.4%CVE-2025-53890CRITICALpyLoad vulnerable to remote code execution through js2py onCaptchaResultEPSS 1.3%CVE-2026-35463HIGHpyLoad has Improper Neutralization of Special Elements used in an OS CommandEPSS 0.8%