Gophish Account Lockout and Forced Password Change Bypassable via API Key
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| gophish | gophish | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Getgophish | Gophish |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.551% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Gophish through 0.12.1 fails to enforce account lockout and password change requirements in the API authentication middleware. Attackers with valid API keys can bypass these security controls and retain full API access even when their account is locked or password change is required. | |
| Title | Gophish Account Lockout and Forced Password Change Bypassable via API Key | |
| First Time appeared |
Getgophish
Getgophish gophish |
|
| Weaknesses | CWE-288 | |
| CPEs | cpe:2.3:a:getgophish:gophish:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Getgophish
Getgophish gophish |
|
| References |
| |
| Metrics |
cvssV3_1
|