getgrav Grav Login Plugin up to 3.8.12 Token Storage TokenStorage.php findTriplet session expiration
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in getgrav Grav Login Plugin up to 3.8.12. This affects the function findTriplet of the file TokenStorage.php of the component Token Storage. The manipulation leads to session expiration.
This vulnerability is documented as CVE-2026-66400. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in getgrav Grav Login Plugin up to 3.8.12 and classified as critical. This issue affects the function findTriplet of the file TokenStorage.php of the component Token Storage. The manipulation with an unknown input leads to a session expiration vulnerability. Using CWE to declare the problem leads to CWE-613. According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Grav Login Plugin versions before 3.8.13 contain an insufficient session expiration vulnerability in TokenStorage.php where the findTriplet() method fails to properly validate Remember Me token timestamps. Attackers with a captured Remember Me cookie can authenticate indefinitely instead of the configured timeout period, as the expiry check compares an array to a scalar value which always evaluates incorrectly in PHP.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-66400 since 07/26/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available.
By approaching the search of inurl:TokenStorage.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 3.8.13 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Session expirationCWE: CWE-613
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Grav Login Plugin 3.8.13
Timeline
07/26/2026 CVE reserved07/29/2026 Advisory disclosed
07/29/2026 VulDB entry created
07/29/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2026-66400 (🔒)
GCVE (CVE): GCVE-0-2026-66400
GCVE (VulDB): GCVE-100-384161
Entry
Created: 07/29/2026 16:17Changes: 07/29/2026 16:17 (57)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.