High severityPHPSensitive Data ExposureMEDIUM confidence
Sensitive Data In Cookie Cleartext
A secret or PII/PHI value is written to a cookie in cleartext (CWE-312).
Standards mapping
- OWASP Top 10
- A02:2021 - Cryptographic Failures
- OWASP ASVS
- V8.3.4 (L2)V8.1.1 (L2)
Vulnerable vs. safe
Flagged by this check
setcookie("token", $jwt);Passes - the safe pattern
setcookie("theme", $theme);Why it matters & how to fix it
A secret or PII/PHI value is written to a cookie in cleartext (CWE-312). Cookies are stored client-side and sent on every request. Never place passwords, tokens, or personal data in a readable cookie; store only an opaque session identifier server-side and set Secure/HttpOnly.
References
Rule ID integsec-php-sensitive-data-in-cookie-cleartext - engine: Opengrep - license: MIT - Copyright (c) IntegSec Inc.
TurboPentest runs this check automatically
Connect a GitHub repo and this check runs on every white-box pentest - AI-validated and reported with proof, from $99 per target.
Start a pentestRelated checks
- JavaScript / TypeScript - Sensitive Data ExposureError Stack In Response
- JavaScript / TypeScript - Sensitive Data ExposurePII PHI In Logs
- JavaScript / TypeScript - Sensitive Data ExposureSecret In Logs
- JavaScript / TypeScript - Sensitive Data ExposureSensitive Data Client Storage
- JavaScript / TypeScript - Sensitive Data ExposureSensitive Data In URL Query
- Python - Sensitive Data ExposureFlask Traceback In Response