# CVE-2023-43295: Cross-site request forgery in n/a

> A local attacker can execute arbitrary code via a crafted request due to a Cross Site Request Forgery vulnerability in Passwordstate.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Oct 2023
- **Updated:** 5 Sep 2024
- **Also known as:** GHSA-mrhc-jwc8-xfc6

## What is CVE-2023-43295?

CVE-2023-43295 is a low-severity vulnerability in n/a, published on 31 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross Site Request Forgery vulnerability in Click Studios (SA) Pty Ltd Passwordstate v.Build 9785 and before allows a local attacker to execute arbitrary code via a crafted request.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2023-43295?

It affects 1 product.


Products: Clickstudios Passwordstate.

## How do I fix CVE-2023-43295?

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

## Is CVE-2023-43295 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-26061](https://insights.sbomify.com/CVE-2020-26061/): Auth bypass in n/a (high 7.5)
- [CVE-2022-3875](https://insights.sbomify.com/CVE-2022-3875/): Click Studios Passwordstate API authentication bypass by assumed-immutable data (high 7.3)
- [CVE-2020-27747](https://insights.sbomify.com/CVE-2020-27747/): Auth bypass in n/a (medium 6.8)
- [CVE-2022-25570](https://insights.sbomify.com/CVE-2022-25570/): Missing authorization in n/a (medium 6.5)
- [CVE-2018-14776](https://insights.sbomify.com/CVE-2018-14776/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-43295 and fix it if it is affected.

What it is: CVE-2023-43295 is a low-severity vulnerability in n/a, published on 31 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-43295 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-2023-43295/ (Markdown: https://insights.sbomify.com/CVE-2023-43295/index.md)
```

## Sources

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

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