High severityPHPHardcoded SecretsMEDIUM confidence
Secret Assigned String Literal
An API key, token, or signing secret is hardcoded as a string literal (CWE-798).
Standards mapping
- OWASP ASVS
- V6.4.1 (L2)V2.10.4 (L2)
Vulnerable vs. safe
Flagged by this check
$api_key = "sk_live_51H8xabcdef0123456789";Passes - the safe pattern
$api_key = getenv("API_KEY");Why it matters & how to fix it
An API key, token, or signing secret is hardcoded as a string literal (CWE-798). Anyone with repository access can read and abuse it, and it cannot be rotated without a code change. Load it from an environment variable (getenv() / $_ENV) or a secrets manager and purge it from history.
References
Rule ID integsec-php-secret-assigned-string-literal - 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