# CVE-2025-22952: Memos Server-Side Request Forgery (SSRF)

> Attackers can exploit insufficient URL validation in Memos to perform Server-Side Request Forgery, potentially accessing internal resources.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Feb 2025
- **Updated:** 3 Mar 2025
- **Also known as:** GHSA-wfxg-v3j4-7qmj, GO-2025-3492

## What is CVE-2025-22952?

CVE-2025-22952 is a critical server-side request forgery vulnerability in Usememos Memos, published on 27 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

elestio memos v0.23.0 is vulnerable to Server-Side Request Forgery (SSRF) due to insufficient validation of user-supplied URLs, which can be exploited to perform SSRF attacks.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-22952?

3 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 to 0.24.0 | None |
| `github.com/usememos/memos` | Go | All versions to 0.24.0 | None |

Products: Usememos Memos.

## How do I fix CVE-2025-22952?

Upgrade to a fixed version.

## Is CVE-2025-22952 being exploited?

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

Public exploit code:

- Elestio Memos <= v0.24.0 - Server-Side Request Forgery (nuclei): http/cves/2025/CVE-2025-22952.yaml

## 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-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)
- [CVE-2022-4851](https://insights.sbomify.com/CVE-2022-4851/): Improper Handling of Values in usememos/memos (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22952 and fix it if it is affected.

What it is: CVE-2025-22952 is a critical server-side request forgery vulnerability in Usememos Memos, published on 27 Feb 2025. 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-2025-22952 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 up to 0.24.0; no fix listed
- github.com/usememos/memos (Go): affected all versions up to 0.24.0; 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-2025-22952/ (Markdown: https://insights.sbomify.com/CVE-2025-22952/index.md)
```

## Sources

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

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