Description
django-page-cms through 2.0.13 fails to properly validate page permissions in admin helper views, allowing any staff account to read arbitrary page content and stored media paths. Attackers with low-privilege staff credentials can enumerate content identifiers and access unpublished drafts, page listings, and file paths without proper authorization checks.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
batiste django-page-cms
Default version status: unaffected
0 to ≤ 2.0.13affected
pkg:pypi/django-page-cmsReferences
- https://github.com/batiste/django-page-cms/issues/244 ↗
- https://github.com/batiste/django-page-cms ↗
- https://github.com/batiste/django-page-cms/blob/bc4cbe6c187d2d4573289c5695ce8dec0556994d/pages/admin/views.py#L174-L178 ↗
- https://github.com/batiste/django-page-cms/blob/bc4cbe6c187d2d4573289c5695ce8dec0556994d/pages/admin/views.py#L226-L229 ↗
- https://github.com/batiste/django-page-cms/blob/bc4cbe6c187d2d4573289c5695ce8dec0556994d/pages/admin/views.py#L35-L36 ↗
- https://www.vulncheck.com/advisories/django-page-cms-through-2.0.13-unauthorized-content-access-via-staff-account ↗