Grav Login Plugin 2.7.0 before 3.9.9 2FA Bypass via Profile Update Form
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| getgrav | grav-plugin-login | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Getgrav | Grav-plugin-login |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.351% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Getgrav
Getgrav grav-plugin-login |
|
| Vendors & Products |
Getgrav
Getgrav grav-plugin-login |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Grav Login plugin 2.7.0 before 3.9.9 contains an authentication bypass in processUserProfile(), which checks that the session user exists but not that a pending front-end 2FA session is fully authorized. Attackers with a victim's password who can publish a page form without an access rule can invoke update_user before completing 2FA to disable twofa_enabled and take over the account. | |
| Title | Grav Login Plugin 2.7.0 before 3.9.9 2FA Bypass via Profile Update Form | |
| Weaknesses | CWE-287 | |
| References |
| |
| Metrics |
cvssV3_1
|