CVE-2026-93455

django-page-cms through 2.0.13 Unauthorized Content Access via Staff Account

Published Sep 18, 2026 CVSS 4.0 · 7.1 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

This vulnerability stems from a failure to validate page permissions in admin helper views, allowing staff users to read arbitrary page content, including unpublished drafts, page listings, and stored media paths. The missing authorization check (CWE-862) compromises confidentiality by exposing sensitive page data to any user with staff credentials, potentially leading to internal data leakage or aiding further attacks. No code execution or escalation of privileges is described, so the primary risk is data disclosure rather than system compromise.

Affected Systems

The flaw is present in django-page-cms versions up to 2.0.13, as maintained by batiste. Administrators using any of these releases that have staff accounts configured for the admin interface are affected.

Risk and Exploitability

The CVSS score of 7.1 indicates a moderate severity, but the EPSS score of less than 1% suggests a very low probability of exploitation under current conditions. The issue is not listed in the CISA KEV catalog, further reducing the risk of widespread exploitation. Attackers require valid staff credentials, implying the vector is a compromised or misconfigured account rather than a remote network attack. If staff accounts are improperly granted, the vulnerability can be exercised locally within the application context, allowing enumeration of page IDs and media paths.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade django-page-cms to a version newer than 2.0.13 where the permission validation is fixed.
  • Limit staff roles to read-only if possible, removing write or admin privileges that enable content enumeration.
  • Revoke or rotate staff credentials that are not strictly required, and enforce two-factor authentication for administrative accounts.

Generated by OpenCVE AI on September 19, 2026 at 21:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Batiste
Batiste django-page-cms
Vendors & Products Batiste
Batiste django-page-cms
Type Values Removed Values Added
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.
Title django-page-cms through 2.0.13 Unauthorized Content Access via Staff Account
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 24, 2026, 2:23 PM
Reserved
Sep 17, 2026, 11:37 PM
Status
Deferred
Published
Sep 18, 2026, 2:17 AM
Modified
Sep 22, 2026, 8:53 PM