# CVE-2018-12104: Airbnb Knowledge Repo XSS In Comments

> Remote attackers can inject arbitrary web scripts via post comments in Airbnb Knowledge Repo, potentially compromising user sessions.

- **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:** Yes
- **Published:** 17 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xmw7-848p-p95w, PYSEC-2018-116

## What is CVE-2018-12104?

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

Cross-site scripting (XSS) vulnerability in Airbnb Knowledge Repo 0.7.4 allows remote attackers to inject arbitrary web scripts or HTML via the post comments functionality, as demonstrated by the post/posts/new_report.kp URI.

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

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

3 open source packages ship an affected version, including knowledge-repo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `knowledge-repo` | PyPI | All versions | 0.7.5 |
| `knowledge-repo` | PyPI | All versions | 0.9.0 |
| `knowledge-repo` | PyPI | All versions | 0.9.0 |

Products: Airbnb Knowledge Repo.

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

Upgrade knowledge-repo to a fixed version for your release line: 0.7.5 or 0.9.0.

## Is CVE-2018-12104 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- knowledge-repo (PyPI): affected all versions; fixed in 0.7.5
- knowledge-repo (PyPI): affected all versions; fixed in 0.9.0
- knowledge-repo (PyPI): affected all versions; fixed in 0.9.0

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-12104/ (Markdown: https://insights.sbomify.com/CVE-2018-12104/index.md)
```

## Sources

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

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