WordPress plugin · checkview
Is CheckView safe?
Safe on 2.5.1 or newer.
The current version, 2.5.1, is past every affected range on record (2 of 2 records list one). Keep it updated and you’re clear of them.
- Flaws on record
- 2
- High or critical
- 2
- Exploited
- none
- Current version
- 2.5.1
- Last updated
- Oct 4, 2026
- Active installs
- 1,000+
Every recorded flaw
- Aug 10, 2026CheckView: 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 beforeCVE-2026-18786 · fixed in 2.3.2 · reported by WPScanHigh 8.8
- Jun 25, 2026Unauthenticated Broken Access Control in CheckView Automated Testing <= 2.1.0 versions.CVE-2026-54844 · affects up to 2.1.0 · reported by PatchstackHigh 7.5
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.