CVE-2024-1063VulnerabilityPublished 30 Jan 2024Updated 29 May 2025

CVE-2024-1063: Appwrite · Server-Side Request Forgery (SSRF)

Affects AppwriteSource CVE Database V5

Mentioned vulnerabilities

CVE-2023-27159

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Appwrite Appwrite	Affected =0 <=1.4.13	Fixed in–

AI-suggested

1. Immediate mitigation involves upgrading Appwrite to a version beyond v1.4.13 once a patch is released that fully addresses CVE-2024-1063. Until then, consider disabling or restricting access to the '/v1/avatars/favicon' endpoint if feasible. 2. Implement network-level controls such as egress filtering to prevent the Appwrite server from making unauthorized outbound requests to internal or sensitive IP ranges, reducing SSRF impact. 3. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious SSRF payloads targeting the vulnerable endpoint. 4. Conduct thorough input validation and sanitization on any URL or host parameters accepted by the application, ensuring only trusted domains or IP addresses are allowed. 5. Monitor application logs for unusual outbound requests or access patterns indicative of SSRF attempts. 6. In cloud environments, restrict metadata service access using provider-specific controls (e.g., AWS IMDSv2 enforcement) to limit SSRF exploitation. 7. Educate development teams on secure coding practices to prevent SSRF and validate that fixes for previous vulnerabilities are comprehensive.

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.

Impact

For European organizations using Appwrite as part of their application infrastructure, this SSRF vulnerability poses a moderate risk primarily related to confidentiality breaches. Attackers could leverage the SSRF flaw to access internal services, potentially extracting sensitive configuration data, internal APIs, or cloud metadata that could be used to escalate privileges or move laterally within the network. Although the vulnerability does not directly affect data integrity or service availability, the information gained could facilitate more severe attacks. Organizations in sectors with strict data protection requirements, such as finance, healthcare, and government, may face compliance risks if internal data is exposed. The risk is heightened in cloud-hosted environments common in Europe, where SSRF can be used to access cloud provider metadata services, potentially exposing credentials or tokens. Since the vulnerability requires no authentication or user interaction, it can be exploited remotely by unauthenticated attackers, increasing the attack surface. However, the lack of known active exploits and the medium severity score suggest the threat is moderate but should be addressed promptly to prevent escalation.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

tenable.com/security/research/tra-2024-03 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 01:26 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats