# CVE-2026-86812: WPCafe 3.0.10 - 3.0.17 - Unauthenticated Order Disclosure and Modification via food-orders REST API

> Unauthenticated attackers can access and modify order data via REST API due to improper permission callback implementation in WPCafe plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-x4jx-c5mg-vj6r

## What is CVE-2026-86812?

CVE-2026-86812 is a medium-severity missing authorization vulnerability in Unknown WPCafe, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WPCafe  WordPress plugin before 3.0.18 does not correctly restrict access to a set of order-management REST endpoints because their permission callbacks return an incorrect type on failure, allowing unauthenticated users to disclose guest order information and to change the status of, or trash, any order.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-86812 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86812 is a medium-severity missing authorization vulnerability in Unknown WPCafe, published on 11 Sep 2026. 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-2026-86812 in the wild and no public exploit code.

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

## Sources

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

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