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.
Published: 2026-08-28
Score: 8.6 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Gophish users with a valid API key can continue to access the API even when their user account has been locked or is required to change its password, thereby bypassing the relief mechanisms that should restrict access after a security incident. This flaw resides in the authentication middleware and permits persistence of unauthorized API privileges for the compromised account.

Affected Systems

All Gophish installations up to and including version 0.12.1 are affected. The vulnerable component is Gophish’s API authentication middleware. Deployments that rely on Gophish’s API for automated actions are susceptible until a patched version is installed.

Risk and Exploitability

The CVSS score of 8.6 signals a high severity vulnerability. The EPSS score is not available, and the flaw is not listed in CISA’s KEV catalog, indicating that widespread exploitation has not yet been reported. The attack vector is inferred to require possession of a valid API key, which an attacker can obtain through credential compromise or misconfiguration. With a key in hand, an attacker can bypass account lockout and forced password change requirements, maintaining persistent API access to the victim’s system.

Generated by OpenCVE AI on August 28, 2026 at 22:15 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Gophish to the latest version that implements proper enforcement of account lockout and forced password change controls.
  • If immediate upgrade is not feasible, revoke all active API keys for accounts that have been locked or are required to change passwords and issue new keys only after the password change has been completed.
  • Enable strict account lockout monitoring and enforce mandatory password changes by configuring the system’s security policy to prevent API access when an account is locked or pending a password change.

Generated by OpenCVE AI on August 28, 2026 at 22:15 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 28 Aug 2026 22:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Fri, 28 Aug 2026 19:45:00 +0000

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

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}

cvssV4_0

{'score': 8.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Getgophish Gophish
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-28T20:29:19.133Z

Reserved: 2026-08-28T11:12:38.112Z

Link: CVE-2026-82269

cve-icon Vulnrichment

Updated: 2026-08-28T20:28:58.488Z

cve-icon NVD

Status : Received

Published: 2026-08-28T20:20:17.650

Modified: 2026-08-28T22:16:55.857

Link: CVE-2026-82269

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-28T22:30:17Z

Weaknesses
  • CWE-288

    Authentication Bypass Using an Alternate Path or Channel