# CVE-2020-24713: Security feature bypass in n/a

> Attackers can maintain unauthorized access after logout because the session cookie is not invalidated, allowing potential account takeover.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Oct 2020
- **Updated:** 4 Aug 2024

## What is CVE-2020-24713?

CVE-2020-24713 is a high-severity vulnerability in n/a, published on 28 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gophish through 0.10.1 does not invalidate the gophish cookie upon logout.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2020-24713?

It affects 1 product.


Products: Getgophish Gophish.

## How do I fix CVE-2020-24713?

No fix has been published for CVE-2020-24713 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-24713 being exploited?

There is no known exploitation of CVE-2020-24713 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-24707](https://insights.sbomify.com/CVE-2020-24707/): Other in n/a (high 7.8)
- [CVE-2025-70963](https://insights.sbomify.com/CVE-2025-70963/): Gophish is vulnerable to Incorrect Access Control (high 7.6)
- [CVE-2022-45003](https://insights.sbomify.com/CVE-2022-45003/): Gophish vulnerable to Denial of Service via crafted payload involving autofocus (high 7.5)
- [CVE-2020-24711](https://insights.sbomify.com/CVE-2020-24711/): Cross-site request forgery in n/a (medium 6.5)
- [CVE-2022-45004](https://insights.sbomify.com/CVE-2022-45004/): Gophish vulnerable to Cross-site Scripting via crafted landing page (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-24713 and fix it if it is affected.

What it is: CVE-2020-24713 is a high-severity vulnerability in n/a, published on 28 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-24713 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-24713/ (Markdown: https://insights.sbomify.com/CVE-2020-24713/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-24713
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-24713
- OSV: https://osv.dev/vulnerability/CVE-2020-24713

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-24713/
Summaries are generated and may contain mistakes; the official description above is the record.