CVE-2025-70963 json
Gophish is vulnerable to Incorrect Access Control
published 2026-02-06 9 mo ago modified 2026-06-17 4 mo ago also GHSA-9f8m-9547-2gqm , GO-2026-4455 , EUVD-2025-206883
- cvss
- 7.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
Gophish <=0.12.1 is vulnerable to Incorrect Access Control. The administrative dashboard exposes each user’s long-lived API key directly inside the rendered HTML/JavaScript of the page on every login. This makes permanent API credentials accessible to any script running in the browser context.
Patch / fix
- govulncheck-vulndb openSUSE Leap 15.6 0.0.20260226T182644-150000.1.149.1
suse advisories SUSE-SU-2026:0757-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 9 mo ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/gophish/gophish/issues/9366 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L |
| CNA | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/gophish/gophish | <=0.12.1 all versions |
no fix listed |
Classification
References
-
github.com
/gophish/gophish/issues/9366
web, exploit, issue-tracking, vendor-advisory, report
-
nvd.nist.gov
/vuln/detail/CVE-2025-70963
advisory
-
github.com
/gophish/gophish
package
-
github.com
/advisories/GHSA-9f8m-9547-2gqm
advisory
Sources
- CVE List CVE-2025-70963
- GitHub Advisory GHSA-9f8m-9547-2gqm
- NVD CVE-2025-70963
- OSV GO-2026-4455
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.