# CVE-2024-1063: Server-side request forgery in Appwrite

> Attackers can exploit an SSRF vulnerability in the favicon endpoint to access internal resources or bypass security controls.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 30 Jan 2024
- **Updated:** 29 May 2025
- **Also known as:** GHSA-vrjf-gppf-qvj4

## What is CVE-2024-1063?

CVE-2024-1063 is a medium-severity server-side request forgery vulnerability in Appwrite, published on 30 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Appwrite <= v1.4.13 is affected by a Server-Side Request Forgery (SSRF) via the '/v1/avatars/favicon' endpoint due to an incomplete fix of CVE-2023-27159.

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

## Which versions are affected by CVE-2024-1063?

It affects 1 product.


Products: Appwrite Appwrite.

## How do I fix CVE-2024-1063?

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

## Is CVE-2024-1063 being exploited?

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

## Other vulnerabilities in Appwrite

- [CVE-2022-2925](https://insights.sbomify.com/CVE-2022-2925/): Cross-site Scripting (XSS) - Stored in appwrite/appwrite (critical 9.0)
- [CVE-2022-25377](https://insights.sbomify.com/CVE-2022-25377/): Appwrite Directory Traversal vulnerability (high 7.5)
- [CVE-2023-27159](https://insights.sbomify.com/CVE-2023-27159/): Appwrite Server-Side Request Forgery vulnerability (high 7.5)
- [CVE-2021-23682](https://insights.sbomify.com/CVE-2021-23682/): Prototype Pollution (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1063 and fix it if it is affected.

What it is: CVE-2024-1063 is a medium-severity server-side request forgery vulnerability in Appwrite, published on 30 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1063 in the wild and no public exploit code.

Affected product: Appwrite. 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-2024-1063/ (Markdown: https://insights.sbomify.com/CVE-2024-1063/index.md)
```

## Sources

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

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