# CVE-2026-0658: Five Star Restaurant Reservations < 2.7.9 - Arbitrary Bookings Deletion via CSRF

> Attackers can trick logged-in admins into deleting restaurant bookings via CSRF due to missing checks in bulk actions.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Feb 2026
- **Updated:** 2 Feb 2026
- **Also known as:** GHSA-xmx6-mr5x-2rqc

## What is CVE-2026-0658?

CVE-2026-0658 is a medium-severity vulnerability in Unknown Five Star Restaurant Reservations, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Five Star Restaurant Reservations  WordPress plugin before 2.7.9 does not have CSRF checks in some bulk actions, which could allow attackers to make logged in admins perform unwanted actions, such as deleting bookings via CSRF attacks.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-0658?


## How do I fix CVE-2026-0658?

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

## Is CVE-2026-0658 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0658 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0658 and fix it if it is affected.

What it is: CVE-2026-0658 is a medium-severity vulnerability in Unknown Five Star Restaurant Reservations, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0658 exists.

Affected product: Unknown Five Star Restaurant Reservations. 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-2026-0658/ (Markdown: https://insights.sbomify.com/CVE-2026-0658/index.md)
```

## Sources

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

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