# CVE-2023-4698: Improper Input Validation in usememos/memos

> Improper input validation in the usememos/memos web application allows attackers to potentially disrupt service or inject malicious data.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/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:** 1 Sep 2023
- **Updated:** 30 Sep 2024
- **Also known as:** GHSA-96gq-6ch5-mm54

## What is CVE-2023-4698?

CVE-2023-4698 is a high-severity vulnerability in Usememos Memos, published on 1 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Input Validation in GitHub repository usememos/memos prior to 0.13.2.

Weakness: CWE-20 (Improper Input Validation)

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

2 open source packages ship an affected version, including github.com/usememos/memos. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/usememos/memos` | Go | All versions | None |
| `github.com/usememos/memos` | Go | All versions | None |

Products: Usememos Memos.

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

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

## Is CVE-2023-4698 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4698 exists.

Public exploit code:

- https://github.com/mnqazi/CVE-2023-4698 (github_poc): https://github.com/mnqazi/CVE-2023-4698

## Other vulnerabilities in Usememos Memos

- [CVE-2025-50738](https://insights.sbomify.com/CVE-2025-50738/): Memos has Cross-Site Scripting (XSS) Vulnerability in Image URLs (critical 9.8)
- [CVE-2025-22952](https://insights.sbomify.com/CVE-2025-22952/): Memos Server-Side Request Forgery (SSRF) (critical 9.8)
- [CVE-2023-0109](https://insights.sbomify.com/CVE-2023-0109/): Stored XSS in usememos/memos (critical 9.8)
- [CVE-2023-4696](https://insights.sbomify.com/CVE-2023-4696/): Improper Access Control in usememos/memos (critical 9.8)
- [CVE-2022-4866](https://insights.sbomify.com/CVE-2022-4866/): Cross-site Scripting (XSS) - Stored in usememos/memos (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4698 is a high-severity vulnerability in Usememos Memos, published on 1 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4698 exists.

Affected packages and fixed versions:
- github.com/usememos/memos (Go): affected all versions; no fix listed
- github.com/usememos/memos (Go): affected all versions; no fix listed

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-4698/ (Markdown: https://insights.sbomify.com/CVE-2023-4698/index.md)
```

## Sources

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

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