# CVE-2024-37952: WordPress BookYourTravel theme <= 8.18.17 - Subscriber+ Privilege Escalation vulnerability

> Attackers with subscriber access can escalate privileges in the BookYourTravel WordPress theme due to improper privilege management.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** 9 Jul 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-mrph-x5vw-m2pr

## What is CVE-2024-37952?

CVE-2024-37952 is a high-severity vulnerability in themeenergy BookYourTravel, published on 9 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Privilege Management vulnerability in themeenergy BookYourTravel allows Privilege Escalation.This issue affects BookYourTravel: from n/a through 8.18.17.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Themeenergy Book Your Travel.

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

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

## Is CVE-2024-37952 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-37952 is a high-severity vulnerability in themeenergy BookYourTravel, published on 9 Jul 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-37952 in the wild and no public exploit code.

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

## Sources

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

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