CVE-2023-50974 — appwrite-cli
MEDIUMCVE-2023-50974 is a medium-severity (CVSS 5.5) Hard-coded Credentials vulnerability in appwrite-cli. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for appwrite-cli — see the affected versions and patch details below.
Apprite CLI makes Use of Hard-coded Credentials
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-50974.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
appwrite-clinpmDescription
In Appwrite CLI before 3.0.0, when using the login command, the credentials of the Appwrite user are stored in a ~/.appwrite/prefs.json file with 0644 as UNIX permissions. Any user of the local system can access those credentials.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | appwrite-cli | all versions | 3.0.0npm install appwrite-cli@3.0.0 |
| 🐍PyPI | appwrite | all versions | 3.0.0pip install --upgrade 'appwrite==3.0.0' |
Affected Products
command line interfaceappwriteResearch 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 dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for appwrite-cli, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update appwrite-cli to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-50974 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2023-50974 in your dependencies?
Find it across npm, PyPI, including transitive dependencies.