# CVE-2023-52289: Path traversal in flaskcode

> Unauthenticated attackers can write to arbitrary files via directory traversal in the flaskcode package, potentially compromising system integrity.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 13 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-v3rg-qm46-xrg9, PYSEC-2026-1387

## What is CVE-2023-52289?

CVE-2023-52289 is a high-severity path traversal vulnerability in n/a, published on 13 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the flaskcode package through 0.0.8 for Python. An unauthenticated directory traversal, exploitable with a POST request to a /update-resource-data/<file_path> URI (from views.py), allows attackers to write to arbitrary files.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2023-52289?

3 open source packages ship an affected version, including flaskcode. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `flaskcode` | PyPI | All versions to 0.0.8 | None |
| `flaskcode` | PyPI | All versions to 0.0.8 | None |
| `flaskcode` | PyPI | All versions to 0.0.8 | None |

Products: Sujeetkv Flaskcode.

## How do I fix CVE-2023-52289?

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

## Is CVE-2023-52289 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-52288](https://insights.sbomify.com/CVE-2023-52288/): Path traversal in flaskcode (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52289 and fix it if it is affected.

What it is: CVE-2023-52289 is a high-severity path traversal vulnerability in n/a, published on 13 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-2023-52289 in the wild and no public exploit code.

Affected packages and fixed versions:
- flaskcode (PyPI): affected all versions up to 0.0.8; no fix listed
- flaskcode (PyPI): affected all versions up to 0.0.8; no fix listed
- flaskcode (PyPI): affected all versions up to 0.0.8; 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-2023-52289/ (Markdown: https://insights.sbomify.com/CVE-2023-52289/index.md)
```

## Sources

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

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