WHartTest 2.2.0 through 2.8.1 contains a missing authorization vulnerability in ScheduledTaskViewSet and TaskExecutionViewSet that allows authenticated users to access other projects' tasks. Attackers can set project_pk to another project's sequential ID to modify, delete, or trigger scheduled tasks via run-now and read execution logs.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 5.3 · mgdaaslabNVD modified 2026-10-30 14:16
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 6
- https://github.com/MGdaasLab/WHartTest/issues/166 issue-tracking
- https://github.com/MGdaasLab/WHartTest/blob/v2.8.1/WHartTest_Django/task_center/views.py#L19-L104 technical-description
- https://github.com/MGdaasLab/WHartTest/blob/v2.8.1/WHartTest_Django/task_center/views.py#L107-L133 technical-description
- https://hackmd.io/@hieuPenguinnn/wharttest-scheduled-task-cross-project-missing-authz-idor third-party-advisory
- https://github.com/MGdaasLab/WHartTest product
- https://www.vulncheck.com/advisories/wharttest-2.2.0-through-2.8.1-missing-authorization-via-task-center-scheduled-task-apis third-party-advisory