# CVE-2026-87918: WPBot < 8.5.7 - Unauthenticated AI Provider API Abuse via Multiple AJAX Actions

> Unauthenticated attackers can abuse AI provider API keys via missing authorization checks in WPBot, causing financial loss through unauthorized API usage.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 12 Sep 2026
- **Updated:** 12 Sep 2026
- **Also known as:** GHSA-54cr-fg97-fjjx

## What is CVE-2026-87918?

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

### Official description

The WPBot  WordPress plugin before 8.5.7 does not perform any authorization or nonce check on several AJAX actions that relay prompts to its configured AI providers, allowing unauthenticated attackers to make those third-party API calls, and consume the associated cost, using the site's own configured API keys.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-87918 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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