# CVE-2024-38699: WordPress Wallet System for WooCommerce plugin <= 2.5.13 - Sensitive Data Exposure via Exported File vulnerability

> Attackers can access sensitive data via exported files due to missing authorization checks in the Wallet System for WooCommerce plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-5pr3-frh5-5p66

## What is CVE-2024-38699?

CVE-2024-38699 is a high-severity missing authorization vulnerability in WP Swings Wallet System for WooCommerce, published on 13 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authorization vulnerability in WP Swings Wallet System for WooCommerce allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Wallet System for WooCommerce: from n/a through 2.5.13.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-38699?


## How do I fix CVE-2024-38699?

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

## Is CVE-2024-38699 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-38699 and fix it if it is affected.

What it is: CVE-2024-38699 is a high-severity missing authorization vulnerability in WP Swings Wallet System for WooCommerce, published on 13 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38699 in the wild and no public exploit code.

Affected product: WP Swings Wallet System for WooCommerce. 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-2024-38699/ (Markdown: https://insights.sbomify.com/CVE-2024-38699/index.md)
```

## Sources

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

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