# CVE-2023-2287: Orbit Fox < 2.10.24 - Author+ Server-Side Request Forgery

> An authenticated user can force the server to access arbitrary URLs via the stock photo import feature, enabling server-side request forgery attacks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 30 May 2023
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-pq5g-3m7v-mf66

## What is CVE-2023-2287?

CVE-2023-2287 is a medium-severity server-side request forgery vulnerability in Unknown Orbit Fox by ThemeIsle, published on 30 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Orbit Fox by ThemeIsle WordPress plugin before 2.10.24 does not limit URLs which may be used for the stock photo import feature, allowing the user to specify arbitrary URLs. This leads to a server-side request forgery as the user may force the server to access any URL of their choosing.

## Which versions are affected by CVE-2023-2287?

It affects 1 product.


Products: Themeisle Orbitfox.

## How do I fix CVE-2023-2287?

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

## Is CVE-2023-2287 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-2287 and fix it if it is affected.

What it is: CVE-2023-2287 is a medium-severity server-side request forgery vulnerability in Unknown Orbit Fox by ThemeIsle, published on 30 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-2287 exists.

Affected product: Unknown Orbit Fox by ThemeIsle. 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-2023-2287/ (Markdown: https://insights.sbomify.com/CVE-2023-2287/index.md)
```

## Sources

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

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