Skip to main content
VulnerabilityPublished

CVE-2026-107270: Gophish through 0.12.1 contains an insecure direct object reference vulnerability that allows authenticated users to take over other users' groups

Affects gophishSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 0.12.2 soon.

Data as of 21 Nov 2026, 17:34 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.12.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade gophish/gophish to 0.12.2.

Affected software

ProductAffectedFixed in
GitHubgophish/gophishpkg:github/gophish/gophishOther threatsAffected
  • <0.12.2
Fixed in
  • 0.12.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict access to authenticated users carefully and monitor for suspicious activity related to object reassignment. Avoid sharing sequential IDs in API requests or implement additional access controls to prevent unauthorized object manipulation.

Description

Gophish versions through 0.12.1 have an insecure direct object reference vulnerability that allows authenticated users to take over other users' groups, templates, landing pages, and sending profiles by supplying another user's sequential ID in certain API POST requests. This can lead to unauthorized reassignment of objects and exposure of recipient lists.

References

Community reviews

Loading reviews…