# CVE-2022-25590: Auth bypass in n/a

> Attackers can hijack user sessions via browser cache after logout, gaining unauthorized access to the application and sensitive data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Mar 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-xxrc-mppm-r6mw

## What is CVE-2022-25590?

CVE-2022-25590 is a medium-severity authentication bypass vulnerability in n/a, published on 25 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SurveyKing v0.2.0 was discovered to retain users' session cookies after logout, allowing attackers to login to the system and access data using the browser cache when the user exits the application.

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

## Which versions are affected by CVE-2022-25590?

It affects 1 product.


Products: Surveyking Surveyking.

## How do I fix CVE-2022-25590?

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

## Is CVE-2022-25590 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-35049](https://insights.sbomify.com/CVE-2024-35049/): Security feature bypass in n/a (critical 9.1)
- [CVE-2024-35050](https://insights.sbomify.com/CVE-2024-35050/): Auth bypass in n/a (high 8.8)
- [CVE-2024-35048](https://insights.sbomify.com/CVE-2024-35048/): Auth bypass in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25590 and fix it if it is affected.

What it is: CVE-2022-25590 is a medium-severity authentication bypass vulnerability in n/a, published on 25 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-25590 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-2022-25590/ (Markdown: https://insights.sbomify.com/CVE-2022-25590/index.md)
```

## Sources

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

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