BOLA authorization bypass in StudioCMS draft content edit endpoint

Repository purpose: a Python Proof-of-Concept exploit for CVE-2026-24134 (Broken Object Level Authorization / IDOR) in StudioCMS <= 0.1.1. The core idea is that authorization checks for draft content were performed client-side, allowing a low-privileged authenticated user (e.g., Visitor) to directly access draft content belonging to higher-privileged users by requesting an endpoint with a known UUID. Structure: - LICENSE: MIT. - README.md: explains the vulnerability, prerequisites (requests, colorama), manual and automated usage, expected status codes (200 vulnerable, 403 patched, etc.), and mitigation guidance. - cve_2026_24134_poc.py: main exploit script. Exploit capabilities (from code/README): - Authenticates to the target via POST /studiocms_api/auth/login and captures the auth_session cookie. - Optionally verifies/infer role by GET /dashboard and searching response text for role keywords. - Performs the BOLA/IDOR attempt by requesting draft content using a user-supplied UUID (the exploit method is truncated in the provided content, but README indicates it accesses an edit/draft content endpoint and treats HTTP 200 as successful unauthorized access). - Can save retrieved draft content to a local file named draft_{uuid}.html. - Provides an automated test mode that logs in as a Visitor and an Editor to validate whether the Visitor can access the same draft UUID, then reports whether the instance is vulnerable. Notable observables: - Network endpoints: /studiocms_api/auth/login and /dashboard are explicitly present in code; the draft-content endpoint is implied by README but not visible due to truncation. - Authentication artifact: auth_session cookie used as the session token. Overall assessment: This is a functional PoC exploit (not just detection) that demonstrates unauthorized access to protected draft content via UUID-based direct object reference, with basic automation and optional data exfiltration to a local HTML file.