# CVE-2022-36350: Cross-site scripting in PukiWiki

> Remote attackers can inject arbitrary scripts into PukiWiki, potentially executing code or stealing data from other users.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Aug 2022
- **Updated:** 30 Jun 2025
- **Also known as:** GHSA-428v-vcmp-3q56

## What is CVE-2022-36350?

CVE-2022-36350 is a medium-severity cross-site scripting vulnerability in PukiWiki, published on 23 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Stored cross-site scripting vulnerability in PukiWiki versions 1.3.1 to 1.5.3 allows a remote attacker to inject an arbitrary script via unspecified vectors.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Pukiwiki Pukiwiki.

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

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

## Is CVE-2022-36350 being exploited?

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

## Other vulnerabilities in PukiWiki

- [CVE-2022-34486](https://insights.sbomify.com/CVE-2022-34486/): Path traversal in PukiWiki (high 7.2)
- [CVE-2022-27637](https://insights.sbomify.com/CVE-2022-27637/): Cross-site scripting in PukiWiki (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36350 is a medium-severity cross-site scripting vulnerability in PukiWiki, published on 23 Aug 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-36350 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-36350/ (Markdown: https://insights.sbomify.com/CVE-2022-36350/index.md)
```

## Sources

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

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