# usememos/memos Cross-Site Request Forgery vulnerability in github.com/usememos/memos

Advisory record · `GHSA-gw9m-2m5v-c6x5`

- **Identifiers:** `GHSA-gw9m-2m5v-c6x5` · `CVE-2022-4845` · `GO-2022-1257`
- **State:** Confirmed
- **Severity:** CVSS 6.7 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 21 Aug 2024
- **Updated:** 3 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Aug 2024, 16:04 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/usememos/memos` (Go): affected `<0.9.1`; fixed in `0.9.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Go package github.com/usememos/memos is vulnerable to Cross-Site Request Forgery in versions before 0.9.1. The source gives few details about the attack conditions or impact. Upgrade to version 0.9.1 or later.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.7 Medium, CVSS 3.0: `CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:H`, from CNA (@huntrdev)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0028, the 20th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 21 Aug 2024. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-gw9m-2m5v-c6x5](https://github.com/advisories/GHSA-gw9m-2m5v-c6x5)
- [OSV: GHSA-gw9m-2m5v-c6x5](https://osv.dev/vulnerability/GHSA-gw9m-2m5v-c6x5)
- <https://github.com/advisories/GHSA-gw9m-2m5v-c6x5>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-4845>
- <https://github.com/usememos/memos/commit/c9bb2b785dc5852655405d5c9ab127a2d5aa3948>
- <https://huntr.dev/bounties/075dbd51-b078-436c-9e3d-7f25cd2e7e1b>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-gw9m-2m5v-c6x5>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-gw9m-2m5v-c6x5/>. Everything for agents: <https://agentprime.io/llms.txt>.
