# CVE-2017-10907: Path traversal in OneThird CMS

> An attacker can read arbitrary files on the server hosting OneThird CMS Show Off due to a directory traversal vulnerability.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:** 22 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r2vq-544h-xw77

## What is CVE-2017-10907?

CVE-2017-10907 is a medium-severity path traversal vulnerability in SpiQe Software OneThird CMS, published on 22 Dec 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in OneThird CMS Show Off v1.85 and earlier. Show Off v1.85 en and earlier allows an attacker to read arbitrary files via unspecified vectors.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Spiqe Onethird Cms Show Off.

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

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

## Is CVE-2017-10907 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10907 is a medium-severity path traversal vulnerability in SpiQe Software OneThird CMS, published on 22 Dec 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10907 in the wild and no public exploit code.

Affected product: SpiQe Software OneThird CMS. 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-10907/ (Markdown: https://insights.sbomify.com/CVE-2017-10907/index.md)
```

## Sources

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

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