# CVE-2017-20106: Lithium Forum Compose Message server-side request forgery

> An attacker can exploit a server-side request forgery vulnerability in the Lithium Forum compose message handler to access internal resources.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-5m2c-33c5-mhvp

## What is CVE-2017-20106?

CVE-2017-20106 is a medium-severity server-side request forgery vulnerability in Lithium Forum, published on 28 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in Lithium Forum 2017 Q1. This issue affects some unknown processing of the component Compose Message Handler. The manipulation of the argument upload_url leads to server-side request forgery. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2017-20106?

It affects 1 product.


Products: Khoros Lithium Forum.

## How do I fix CVE-2017-20106?

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

## Is CVE-2017-20106 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20106 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-20106 and fix it if it is affected.

What it is: CVE-2017-20106 is a medium-severity server-side request forgery vulnerability in Lithium Forum, published on 28 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20106 exists.

Affected product: Lithium Forum. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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