pyload-ng: getUserData/get_userdata exposed at Perms.ANY allow any authenticated account to brute-force the administrator password
Description
pyload-ng contains an authentication bypass vulnerability in its API endpoints getUserData and get_userdata, which are accessible to any authenticated user regardless of permission level due to a flawed permission check. This allows low-privileged users to brute-force the administrator password without lockout or effective rate limiting, potentially leading to full administrative takeover.
CVSS v3.1
Score 8.1high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The pyload-ng API exposes two endpoints, getUserData and get_userdata, which are annotated with @permission(Perms.ANY). Since Perms.ANY equals zero and the permission check uses a bitmask AND operation, this gate always returns true for any authenticated user, including those with zero permissions. These endpoints wrap the check_auth() method, which is intended to be admin-only, effectively undoing its protection. An attacker with a low-privileged account can use these endpoints as a binary oracle to brute-force the administrator password. There is no account lockout mechanism, and the rate limiting based on the X-Forwarded-For header is easily bypassed by rotating this header. This vulnerability was verified on version 0.5.0b3 and allows an attacker to recover the admin password and gain full administrative access.
Potential Impact
An attacker with any authenticated account can perform an online brute-force attack against the administrator password without triggering lockout or effective rate limiting, due to the flawed permission check and bypassable rate limiting. Successful exploitation leads to full administrative takeover and disclosure of sensitive administrator account details such as id, name, email, role, and permissions.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the API endpoints getUserData and get_userdata to trusted users only, and consider implementing external rate limiting and monitoring for unusual authentication attempts. Avoid relying on the X-Forwarded-For header for rate limiting without validation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-68w4-83fh-f2w8
- Osv Schema Version
- 1.4.0
- Ecosystems
- ["PyPI"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6ac96e5f2cdf04f65689a8f9
Added to database: 10/09/2026, 22:44:47 UTC
Last enriched: 10/09/2026, 22:53:20 UTC
Last updated: 10/09/2026, 22:53:20 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.