Cookie forgery via empty validation key
Published Sep 7, 2026 · Updated Sep 7, 2026
Cookie validation weakness in FeehiCMS 2.1.0 and 2.1.1 allows remote attackers to forge Yii2-managed cookies with an empty key. The production backend and frontend templates assign cookieValidationKey an empty string, while initialization and Docker startup do not generate a secret. Identity-cookie abuse requires nondefault auto-login and the correct Yii2 serialization format; otherwise the exposed key breaks cookie and CSRF-token integrity.
Summary
What happened
Cookie validation weakness in FeehiCMS 2.1.0 and 2.1.1 allows remote attackers to forge Yii2-managed cookies with an empty key. The production backend and frontend templates assign cookieValidationKey an empty string, while initialization and Docker startup do not generate a secret. Identity-cookie abuse requires nondefault auto-login and the correct Yii2 serialization format; otherwise the exposed key breaks cookie and CSRF-token integrity.
The record
- CVE
- CVE-2026-86241
- Published
- Sep 7, 2026
- Updated
- Sep 7, 2026
- Vendor
- liufee
- Product
- FeehiCMS
- Classifications
- CWE-320, CWE-321, T1606.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 7, 2026CVE publishedPublication date reported by the CVE source.
- Sep 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.1.0
- Affected versionversion=2.1.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- FEHI-003 Empty cookieValidationKey proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo