# Gitea allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text in code.gitea.io/gitea

Advisory record · `GHSA-898p-hh3p-hf9r`

- **Identifiers:** `GHSA-898p-hh3p-hf9r` · `BIT-gitea-2025-68942` · `CVE-2025-68942` · `GO-2025-4263`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md)
- **Published:** 30 Dec 2025
- **Updated:** 3 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 30 Dec 2025, 01:49 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `code.gitea.io/gitea` (Go): affected `<1.22.2`; fixed in `1.22.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Gitea versions before 1.22.2 are vulnerable to cross-site scripting through the search input box used when creating tags and branches, because the input is rendered with v-html rather than v-text. The source gives few details about what the attacker must do to trigger it. Upgrade to Gitea 1.22.2 or later, which contains the fix.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`, from CNA (mitre)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0025, the 16th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 30 Dec 2025. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-898p-hh3p-hf9r](https://github.com/advisories/GHSA-898p-hh3p-hf9r)
- [OSV: GHSA-898p-hh3p-hf9r](https://osv.dev/vulnerability/GHSA-898p-hh3p-hf9r)
- <https://github.com/advisories/GHSA-898p-hh3p-hf9r>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-68942>
- <https://blog.gitea.com/release-of-1.22.2>
- <https://github.com/go-gitea/gitea/pull/31966>
- <https://github.com/go-gitea/gitea/releases/tag/v1.22.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-898p-hh3p-hf9r>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-898p-hh3p-hf9r/>. Everything for agents: <https://agentprime.io/llms.txt>.
