# CVE-2022-4729: Graphite Web Template Name cross site scripting

> Remote attackers can execute arbitrary scripts in Graphite Web via the Template Name Handler, requiring a patch to mitigate.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Dec 2022
- **Updated:** 10 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-4729, GHSA-q99p-78hp-xg5c, PYSEC-2026-820, UBUNTU-CVE-2022-4729

## What is CVE-2022-4729?

CVE-2022-4729 is a low-severity cross-site scripting vulnerability in Graphite Web, published on 24 Dec 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in Graphite Web and classified as problematic. This issue affects some unknown processing of the component Template Name Handler. The manipulation leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 2f178f490e10efc03cd1d27c72f64ecab224eb23. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-216743.

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

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

3 open source packages ship an affected version, including graphite-web. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `graphite-web` | PyPI | All versions to 1.1.10 | None |
| `graphite-web` | PyPI | All versions to 1.1.10 | None |
| `graphite-web` | PyPI | All versions to 1.1.10 | None |

Products: Graphite Project Graphite.

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

Apply the vendor's patch.

## Is CVE-2022-4729 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4729 exists.

## Other vulnerabilities in Graphite Web

- [CVE-2017-18638](https://insights.sbomify.com/CVE-2017-18638/): graphite.composer.views.send_email vulnerable to SSRF (high 7.5)
- [CVE-2013-5093](https://insights.sbomify.com/CVE-2013-5093/): graphite-web is vulnerable to Remote Code Execution via renderLocalView function (medium 6.8)
- [CVE-2013-5942](https://insights.sbomify.com/CVE-2013-5942/): graphite-web is vulnerable to Remote Code Execution (medium 6.8)
- [CVE-2013-5943](https://insights.sbomify.com/CVE-2013-5943/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2022-4728](https://insights.sbomify.com/CVE-2022-4728/): Graphite Web Cookie cross site scripting (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4729 is a low-severity cross-site scripting vulnerability in Graphite Web, published on 24 Dec 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4729 exists.

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

## Sources

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

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