# CVE-2023-6289: Swift Performance Lite <= 2.3.6.14 - Unauthenticated Configuration Export

> Unauthenticated attackers can export plugin settings, potentially exposing sensitive data like Cloudflare API tokens.

- **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:** 18 Dec 2023
- **Updated:** 7 May 2025
- **Also known as:** GHSA-pr5v-xq9x-gp8m

## What is CVE-2023-6289?

CVE-2023-6289 is a medium-severity vulnerability in Unknown Swift Performance Lite, published on 18 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Swift Performance Lite WordPress plugin before 2.3.6.15 does not prevent users from exporting the plugin's settings, which may include sensitive information such as Cloudflare API tokens.

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

It affects 1 product.


Products: Swteplugins Swift Performance.

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

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

## Is CVE-2023-6289 being exploited?

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

Public exploit code:

- Swift Performance Lite <= 2.3.6.14 - Missing Authorization to Unauthenticated Settings Export (github_poc): https://github.com/RandomRobbieBF/CVE-2023-6289

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6289 is a medium-severity vulnerability in Unknown Swift Performance Lite, published on 18 Dec 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-6289 exists.

Affected product: Unknown Swift Performance Lite. 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-6289/ (Markdown: https://insights.sbomify.com/CVE-2023-6289/index.md)
```

## Sources

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

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