pyLoad vulnerable to remote code execution by download to /.pyload/scripts using /flashgot API
Published Oct 25, 2024 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
pyLoad vulnerable to remote code execution by download to /.pyload/scripts using /flashgot API
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
The folder /.pyload/scripts has scripts which are run when certain actions are completed, for e.g. a download is finished. By downloading a executable file to a folder in /scripts and performing the respective action, remote code execution can be achieved. A file can be downloaded to such a folder by changing the download folder to a folder in /scripts path and using the /flashgot API to download the file.
Potential impact
This vulnerability allows an attacker with access to change the settings on a pyload server to execute arbitrary code and completely compromise the system
Technical context
Configuration changes 1. Change the download folder to /home/<user>/.pyload/scripts 2. Change permissions for downloaded files: Making the request to download files The flashgot API provides functionality to download files from a provided URL. Although pyload tries to prevent non-local requests from being able to reach this API, it relies on checking the Host header and the Referer header of the incoming request. Both of these can be set by an attacker to arbitrary values, thereby bypassing these checks. Referer header check Host header check for local check Once the file is downloaded to a folder in the scripts folder, the attacker can perform the respective action, and the script will be executed
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Oct 25, 2024 · Last refreshed Nov 3, 2026