# CVE-2018-7302: Tiki Wiki CMS XSS Vulnerability

> Attackers can upload malicious SVG files disguised as PNGs to execute arbitrary scripts in the victim's browser.

- **Severity:** Medium 5.4 (`CVSS:3.0/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:** 21 Feb 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7f2f-crxg-cpfv

## What is CVE-2018-7302?

CVE-2018-7302 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Feb 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Tiki 17.1 allows upload of a .PNG file that actually has SVG content, leading to XSS.

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

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

2 open source packages ship an affected version, including tikiwiki/tiki-manager. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tikiwiki/tiki-manager` | Packagist | All versions to 17.1 | None |
| `tikiwiki/tiki-manager` | Packagist | All versions to 17.1 | None |

Products: Tiki Tiki.

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

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

## Is CVE-2018-7302 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15906](https://insights.sbomify.com/CVE-2020-15906/): Auth bypass in n/a (critical 9.8)
- [CVE-2023-22850](https://insights.sbomify.com/CVE-2023-22850/): Deserialization in n/a (high 8.8)
- [CVE-2023-22853](https://insights.sbomify.com/CVE-2023-22853/): Code injection in n/a (high 8.8)
- [CVE-2018-7304](https://insights.sbomify.com/CVE-2018-7304/): Code injection in n/a (high 8.8)
- [CVE-2023-22851](https://insights.sbomify.com/CVE-2023-22851/): Deserialization in n/a (high 7.2)

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- tikiwiki/tiki-manager (Packagist): affected all versions up to 17.1; no fix listed
- tikiwiki/tiki-manager (Packagist): affected all versions up to 17.1; 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-7302/ (Markdown: https://insights.sbomify.com/CVE-2018-7302/index.md)
```

## Sources

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

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