MyMangaDB: Unauthenticated path traversal in cover-image upload allows arbitrary file write, escalating to the same database-overwrite takeover
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| FabianRolfMatthiasNoll | MyMangaDB | affected |
|
No data.
No data.
No data available yet.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | MyMangaDB is a self-hosted manga collection manager with automatic metadata, MyAnimeList import, Docker support, and collection statistics. Prior to 2.7.2, the unauthenticated /api/v1/images/manga/save handler in backend/app/api/v1/endpoints/image.py accepts a client-controlled filename and joins it to IMAGE_SAVE_PATH without confining the result. Traversal sequences can escape the image directory and overwrite process-writable files, including DATABASE_PATH for the live SQLite database, while the client-supplied image content type does not validate the uploaded bytes. An attacker can replace the database to plant an administrative user and can overwrite other writable files, causing full application compromise and availability loss. This issue is fixed in version 2.7.2. | |
| Title | MyMangaDB: Unauthenticated path traversal in cover-image upload allows arbitrary file write, escalating to the same database-overwrite takeover | |
| Weaknesses | CWE-22 CWE-306 |
|
| References |
| |
| Metrics |
cvssV4_0
|
No data.
No data.
No data.
No data.
No data.