# CVE-2022-3206: Passster < 3.5.5.5.2 - Insecure Storage of Password

> Attackers can recover user passwords from base64-encoded cookies, leading to potential account takeover if cookies are leaked.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 17 Oct 2022
- **Updated:** 14 May 2025
- **Also known as:** GHSA-7j63-969g-r2jp

## What is CVE-2022-3206?

CVE-2022-3206 is a medium-severity vulnerability in Unknown Passster, published on 17 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Passster WordPress plugin before 3.5.5.5.2 stores the password inside a cookie named "passster" using base64 encoding method which is easy to decode. This puts the password at risk in case the cookies get leaked.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


Products: Passster Project Passster.

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

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

## Is CVE-2022-3206 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3206 is a medium-severity vulnerability in Unknown Passster, published on 17 Oct 2022. 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-2022-3206 in the wild and no public exploit code.

Affected product: Unknown Passster. 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-3206/ (Markdown: https://insights.sbomify.com/CVE-2022-3206/index.md)
```

## Sources

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

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