# CVE-2018-12290: Yii2-StateMachine extension for Yii2 XSS Vulnerability

> An attacker can execute arbitrary scripts in the context of other users via the Yii2-StateMachine extension for Yii2.

- **Severity:** Medium 6.1 (`CVSS:3.0/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:** 13 Jun 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-65qg-f77j-cccf

## What is CVE-2018-12290?

CVE-2018-12290 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Jun 2018. 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

The Yii2-StateMachine extension v2.x.x for Yii2 has XSS.

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

## Which versions are affected by CVE-2018-12290?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ptheofan/yii2-statemachine` | Packagist | From 2.0.0-RC1 to 2.0.0 | None |
| `ptheofan/yii2-statemachine` | Packagist | From 2.0.0-RC1 to 2.0.0 | None |

Products: Yii2-Statemachine Yii2-Statemachine.

## How do I fix CVE-2018-12290?

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

## Is CVE-2018-12290 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12290 and fix it if it is affected.

What it is: CVE-2018-12290 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Jun 2018. 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-2018-12290 in the wild and no public exploit code.

Affected packages and fixed versions:
- ptheofan/yii2-statemachine (Packagist): affected from 2.0.0-RC1 up to 2.0.0; no fix listed
- ptheofan/yii2-statemachine (Packagist): affected from 2.0.0-RC1 up to 2.0.0; 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-2018-12290/ (Markdown: https://insights.sbomify.com/CVE-2018-12290/index.md)
```

## Sources

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

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