# CVE-2022-34297: Yii2 Gii Cross-site Scripting vulnerability

> Attackers can inject malicious scripts into Yii2 Gii fields, leading to stored XSS and potential code execution in the browser context.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-x87m-36g7-6mpw

## What is CVE-2022-34297?

CVE-2022-34297 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Yii Yii2 Gii through 2.2.4 allows stored XSS by injecting a payload into any field.

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

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

2 open source packages ship an affected version, including yiisoft/yii2-gii. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `yiisoft/yii2-gii` | Packagist | All versions to 2.2.4 | None |
| `yiisoft/yii2-gii` | Packagist | All versions to 2.2.4 | None |

Products: Yiiframework Gii.

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

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

## Is CVE-2022-34297 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-36655](https://insights.sbomify.com/CVE-2020-36655/): Command injection in yiisoft/yii2-gii (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34297 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-34297 in the wild and no public exploit code.

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

## Sources

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

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