# CVE-2022-29351: File upload in n/a

> Attackers can execute arbitrary code by uploading a crafted SVG file in TiddlyWiki5, though the vendor disputes this vulnerability.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 May 2022
- **Updated:** 9 Jul 2026

## What is CVE-2022-29351?

CVE-2022-29351 is a critical vulnerability in n/a, published on 16 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An arbitrary file upload vulnerability in the file upload module of Tiddlywiki5 v5.2.2 allows attackers to execute arbitrary code via a crafted SVG file. Note: The vendor argues that this is not a legitimate issue and there is no vulnerability here.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2022-29351?

It affects 1 product.


Products: Tiddlywiki Tiddlywiki5.

## How do I fix CVE-2022-29351?

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

## Is CVE-2022-29351 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29351 and fix it if it is affected.

What it is: CVE-2022-29351 is a critical vulnerability in n/a, published on 16 May 2022. 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-2022-29351 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2022-29351/ (Markdown: https://insights.sbomify.com/CVE-2022-29351/index.md)
```

## Sources

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

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