# CVE-2026-96524: MCP Server for WordPress < 1.8.2 - Administrator Account Creation via CSRF

> Unauthenticated attackers can create administrator accounts by tricking logged-in admins into visiting crafted pages due to missing nonce verification.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 26 Sep 2026
- **Updated:** 26 Sep 2026
- **Also known as:** GHSA-9frx-mgw6-jh42

## What is CVE-2026-96524?

CVE-2026-96524 is a high-severity vulnerability in Unknown MCP Server for WordPress, published on 26 Sep 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 MCP Server for WordPress  WordPress plugin before 1.8.2 does not correctly verify the WordPress REST API nonce for cookie-authenticated requests when a condition an attacker can influence is present, allowing unauthenticated attackers to perform administrator-only actions, including creating a new administrator account, by tricking a logged-in administrator into visiting a crafted page.

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

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


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

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

## Is CVE-2026-96524 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96524 is a high-severity vulnerability in Unknown MCP Server for WordPress, published on 26 Sep 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: There is no known exploitation of CVE-2026-96524 in the wild and no public exploit code.

Affected product: Unknown MCP Server for WordPress. 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-96524/ (Markdown: https://insights.sbomify.com/CVE-2026-96524/index.md)
```

## Sources

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

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