# CVE-2017-20287: Javo Spot WordPress Theme < 3.0.0 Path Traversal via admin-ajax.php fn Parameter


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-f9g9-m55p-h787

## What is CVE-2017-20287?

CVE-2017-20287 is a high-severity vulnerability in Javo Spot, published on 22 Oct 2026. 

### Official description

Javo Spot theme for WordPress before 3.0.0 contains a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files via the fn parameter of the jvfrm_spot_get_json AJAX action. Attackers can send GET requests to /wp-admin/admin-ajax.php with fn set to ../../wp-config.php to retrieve database credentials and secret keys. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-19.

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

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


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

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

## Is CVE-2017-20287 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-20287 is a high-severity vulnerability in Javo Spot, published on 22 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20287 exists.

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

## Sources

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

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