WordPress plugin · wp-verify-api
Is WP Verify API safe?
Closed. Replace it.
wordpress.org closed it on Sep 17, 2026, so it gets no more security fixes, and 2 flaws are on record. If your site runs it, move to a maintained alternative.
- Flaws on record
- 2
- High or critical
- 1
- Exploited
- none
Every recorded flaw
- Oct 11, 2026WP Verify API: Does not properly sanitize and escape a parameter before using it in a SQL queryCVE-2026-89299 · affects up to 1.0.0 · reported by WPScanHigh 8.6
- Sep 28, 2026WP Verify API: Does not have any authorisation check in one of its REST routesCVE-2026-89300 · affects up to 1.0.0 · reported by WPScanMedium 5.3
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.