# CVE-2022-35174: Cross site scripting in getkirby/starterkit

> Attackers can execute arbitrary scripts via stored XSS in the Tags field of Kirby's Starterkit, potentially compromising user sessions.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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:** No
- **Published:** 18 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4m2g-668v-jwjx

## What is CVE-2022-35174?

CVE-2022-35174 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Aug 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 stored cross-site scripting (XSS) vulnerability in Kirby's Starterkit v3.7.0.2 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Tags field.

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

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

2 open source packages ship an affected version, including getkirby/starterkit. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `getkirby/starterkit` | Packagist | All versions to 3.7.0.2 | None |
| `getkirby/starterkit` | Packagist | All versions to 3.7.0.2 | None |

Products: Getkirby Starterkit.

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

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

## Is CVE-2022-35174 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-35174 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Aug 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-35174 in the wild and no public exploit code.

Affected packages and fixed versions:
- getkirby/starterkit (Packagist): affected all versions up to 3.7.0.2; no fix listed
- getkirby/starterkit (Packagist): affected all versions up to 3.7.0.2; 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-35174/ (Markdown: https://insights.sbomify.com/CVE-2022-35174/index.md)
```

## Sources

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

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