# CVE-2024-37106: WordPress WishList Member X plugin < 3.26.7 - Unautenticated Plugin Settings Change Leading to Stored XSS vulnerability

> Unauthenticated attackers can modify plugin settings to inject stored XSS payloads, potentially compromising user sessions and site integrity.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-xm6v-h562-fh85

## What is CVE-2024-37106?

CVE-2024-37106 is a high-severity missing authorization vulnerability in WishList Member X, published on 1 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authorization vulnerability in WishList Products WishList Member X allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WishList Member X: from n/a through 3.26.6

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2024-37106 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-37106 is a high-severity missing authorization vulnerability in WishList Member X, published on 1 Nov 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-37106 in the wild and no public exploit code.

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

## Sources

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

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