Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

CVE-2023-27159

HIGH

CVE-2023-27159 is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in appwrite/server-ce. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2023-27159 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Appwrite Server-Side Request Forgery vulnerability

Also known asGHSA-hxgx-584x-vwm8
Published
Mar 31, 2023
Updated
Jul 15, 2026
Affected
1 pkg
Patched
None yet
Exploits
3 known
Exploitation data as of Jul 15, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐘appwrite/server-ce

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Appwrite up to v1.2.1 was discovered to contain a Server-Side Request Forgery (SSRF) via the component /v1/avatars/favicon. This vulnerability allows attackers to access network resources and sensitive information via a crafted GET request.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐘Packagistappwrite/server-ceall versionsNo fix
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for appwrite/server-ce. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of appwrite/server-ce has shipped for CVE-2023-27159 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2023-27159 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-27159. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Appwrite up to v1.2.1 was discovered to contain a Server-Side Request Forgery (SSRF) via the component /v1/avatars/favicon. This vulnerability allows attackers to access network resources and sensitive information via a crafted GET request.
O3 Security · Impact-Aware SCA

Is CVE-2023-27159 in your dependencies?

O3 detects CVE-2023-27159 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

CVE-2023-27159: Appwrite Server-Side… | O3 Security