# CVE-2022-34486: Path traversal in PukiWiki

> An authenticated administrator can exploit a path traversal flaw in PukiWiki to execute malicious scripts on the server.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-w4fw-hp52-r4mg

## What is CVE-2022-34486?

CVE-2022-34486 is a high-severity path traversal vulnerability in PukiWiki, published on 23 Aug 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Path traversal vulnerability in PukiWiki versions 1.4.5 to 1.5.3 allows a remote authenticated attacker with an administrative privilege to execute a malicious script via unspecified vectors.

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

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

It affects 1 product.


Products: Pukiwiki Pukiwiki.

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

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

## Is CVE-2022-34486 being exploited?

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

## Other vulnerabilities in PukiWiki

- [CVE-2022-27637](https://insights.sbomify.com/CVE-2022-27637/): Cross-site scripting in PukiWiki (medium 6.1)
- [CVE-2022-36350](https://insights.sbomify.com/CVE-2022-36350/): Cross-site scripting in PukiWiki (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34486 is a high-severity path traversal vulnerability in PukiWiki, published on 23 Aug 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-34486 in the wild and no public exploit code.

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

## Sources

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

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