Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
2.9
pyLoad: Users Can Access Data After Permission Changes
GHSA-fj52-5g4h-gmq8
Summary
If a user's permissions are changed in pyLoad, the application doesn't properly update their session. This means a user might still access data they shouldn't have access to. To protect your data, ensure you update user sessions immediately after changing their permissions.
What to do
No fix is available yet. Check with your software vendor for updates.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| pip | – | pyload-ng | <= 0.5.0b3.dev97 |
Original title
pyLoad's Session Not Invalidated After Permission Changes
Original description
### Summary
The `pyload` application does not properly invalidate or modify sessions upon changes made to a user's permissions.
### Details
Whenever an administrator changes the permissions a specific account has, they do not expect that account still being able to access data that their new permissions do not allow. This is not the case for the `pyload` application, as a user with a valid session can still perform the actions.
### PoC
Take a user with all the permissions, as shown below.
We now log in as this user.
Let us now take away all the permissions.
The logged in session can still be used to access everything in the application.
### Impact
Should permissions be taken away, then the user is expected not to be able to execute the actions belonging to those actions anymore.
The `pyload` application does not properly invalidate or modify sessions upon changes made to a user's permissions.
### Details
Whenever an administrator changes the permissions a specific account has, they do not expect that account still being able to access data that their new permissions do not allow. This is not the case for the `pyload` application, as a user with a valid session can still perform the actions.
### PoC
Take a user with all the permissions, as shown below.
We now log in as this user.
Let us now take away all the permissions.
The logged in session can still be used to access everything in the application.
### Impact
Should permissions be taken away, then the user is expected not to be able to execute the actions belonging to those actions anymore.
ghsa CVSS4.0
2.9
Vulnerability type
CWE-613
Published: 14 Apr 2026 · Updated: 15 Apr 2026 · First seen: 15 Apr 2026