High severityPHPHardcoded SecretsMEDIUM confidence
JWT Hardcoded Signing Secret
A JWT signing/verification secret is hardcoded (CWE-798/CWE-321).
Standards mapping
- OWASP Top 10
- A02:2021 - Cryptographic Failures
- OWASP ASVS
- V6.4.1 (L2)
Vulnerable vs. safe
Flagged by this check
return JWT::encode($payload, "supersecretjwtkey", "HS256");Passes - the safe pattern
return JWT::encode($payload, getenv("JWT_SECRET"), "HS256");Why it matters & how to fix it
A JWT signing/verification secret is hardcoded (CWE-798/CWE-321). Anyone who reads the source can forge or validate tokens. Load the signing secret from an environment variable or secrets manager and rotate the exposed key.
References
Rule ID integsec-php-jwt-hardcoded-signing-secret - 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 - Hardcoded SecretsBasic Auth Credentials In URL
- JavaScript / TypeScript - Hardcoded SecretsDB Connection String With Credentials
- JavaScript / TypeScript - Hardcoded SecretsHardcoded Credential String
- JavaScript / TypeScript - Hardcoded SecretsHardcoded Crypto Key Or IV
- Python - Hardcoded SecretsBasic Auth Credentials In URL
- Python - Hardcoded SecretsDB Connection String Credentials