# CVE-2026-18786: CheckView < 2.3.2 - Administrator Account Creation via REST API Authentication Bypass


- **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
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-8r6g-r9rq-8jr8

## What is CVE-2026-18786?

CVE-2026-18786 is a high-severity vulnerability in Unknown CheckView, published on 10 Aug 2026. 

### Official description

The CheckView  WordPress plugin before 2.3.2 does not restrict its REST API authentication filter to its own routes and unconditionally discards the authentication error raised for any request whose URI merely contains a CheckView  WordPress plugin before 2.3.2-specific string, making it possible for unauthenticated attackers to bypass the REST nonce check and perform any REST action available to a logged-in administrator, such as creating a new administrator account, via a crafted link an administrator is tricked into opening.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-18786 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18786 is a high-severity vulnerability in Unknown CheckView, published on 10 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-18786 in the wild and no public exploit code.

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

## Sources

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

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