# CVE-2024-37109: WordPress WishList Member X plugin < 3.26.7 - Authenticated Arbitrary PHP Code Execution vulnerability

> Authenticated attackers can execute arbitrary PHP code in the WishList Member X WordPress plugin, requiring an upgrade to secure the site.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 24 Jun 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-x6pp-pchx-wvc7

## What is CVE-2024-37109?

CVE-2024-37109 is a critical code injection vulnerability in Membership Software WishList Member X, published on 24 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Control of Generation of Code ('Code Injection') vulnerability in Membership Software WishList Member X allows Code Injection.This issue affects WishList Member X: from n/a before 3.26.7.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Wishlistmember Wishlist Member.

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

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

## Is CVE-2024-37109 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-37109 is a critical code injection vulnerability in Membership Software WishList Member X, published on 24 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-37109 in the wild and no public exploit code.

Affected product: Membership Software WishList Member X. 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-37109/ (Markdown: https://insights.sbomify.com/CVE-2024-37109/index.md)
```

## Sources

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

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