| Title | liufee feehi cms 2.1.1 配置错误 |
|---|
| Description | FeehiCMS 2.1.1 ships with an empty cookieValidationKey in all environment templates, including production (environments/prod/backend/config/main-local.php and environments/prod/frontend/config/main-local.php). The Yii2 framework uses this key to sign cookies via HMAC-SHA256. An empty key allows attackers to forge any Yii2-managed cookie, including identity cookies (when enableAutoLogin is enabled) and CSRF tokens.
The docker-entrypoint.sh init script does not auto-generate a random key, so Docker deployments use the empty key by default.
Impact:
Cookie integrity failure, potential authentication bypass, CSRF protection bypass.
Proof of Concept (theoretical):
An attacker can compute HMAC-SHA256(cookie_value, '') to forge a valid Yii2 cookie because the key is empty.
Remediation:
Auto-generate a random 32-byte key during init, add empty-key detection at startup, generate key in Docker entrypoint.
References:
- https://github.com/liufee/cms
- https://github.com/liufee/cms/issues/96
- Full report: https://github.com/yang5ynag/cve/blob/main/FEHI-003-Empty-cookieValidationKey.md |
|---|
| User | lyang (UID 100042) |
|---|
| Submission | 07/22/2026 08:25 (2 months ago) |
|---|
| Moderation | 09/06/2026 10:59 (2 months later) |
|---|
| Status | Accepted |
|---|
| VulDB entry | 399398 [liufee FeehiCMS up to 2.1.1 Cookie Validation main-local.php cookieValidationKey hard-coded key] |
|---|
| Points | 17 |
|---|