Will It Vibe?Django session cookie HttpOnly disabled
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
Django SESSION_COOKIE_HTTPONLY is set to False, exposing the session cookie to any JavaScript on the page and turning an XSS bug into session theft.
Why it matters
SESSION_COOKIE_HTTPONLY = False makes the Django session cookie readable by JavaScript. That removes the one protection that keeps a cross-site scripting bug from immediately becoming full session theft: with HttpOnly off, any injected script can read document.cookie and exfiltrate the session id. Django defaults this to True for good reason.
How to fix it
Set SESSION_COOKIE_HTTPONLY = True (Django defaults to this, so usually the safe fix is to delete the override). Only server-side code needs the session cookie, never client JavaScript. If some feature was reading the session cookie in the browser, redesign it to use a separate, non-sensitive value.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo