# CVE-2017-18585: Path traversal in n/a

> An attacker can exploit a directory traversal vulnerability in the posts-in-page WordPress plugin to read arbitrary files from the server.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mw9c-3h7g-2xc4

## What is CVE-2017-18585?

CVE-2017-18585 is a high-severity path traversal vulnerability in n/a, published on 22 Aug 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The posts-in-page plugin before 1.3.0 for WordPress has ic_add_posts template='../ directory traversal.

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

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

It affects 1 product.


Products: Ivycat Posts in Page.

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

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

## Is CVE-2017-18585 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18585 is a high-severity path traversal vulnerability in n/a, published on 22 Aug 2019. 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-18585 in the wild and no public exploit code.

Affected product: n/a. 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-18585/ (Markdown: https://insights.sbomify.com/CVE-2017-18585/index.md)
```

## Sources

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

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