# CVE-2024-5071: Bookster <= 1.1.0 - Unauthenticated Appointment Status Update

> Unauthenticated attackers can manipulate appointment status from pending to approved by modifying request parameters in the Bookster WordPress plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 26 Jun 2024
- **Updated:** 28 Oct 2024
- **Also known as:** GHSA-xv7j-wg82-2r7g

## What is CVE-2024-5071?

CVE-2024-5071 is a medium-severity missing authorization vulnerability in Unknown Bookster , published on 26 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Bookster  WordPress plugin through 1.1.0 allows adding sensitive parameters when validating appointments allowing attackers to manipulate the data sent when booking an appointment (the request body) to change its status from pending to approved.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Wpbookster Bookster.

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

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

## Is CVE-2024-5071 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5071 is a medium-severity missing authorization vulnerability in Unknown Bookster , published on 26 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-5071 in the wild and no public exploit code.

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

## Sources

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

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