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

> Unauthenticated attackers can modify WP Hide plugin settings due to missing authorization and CSRF checks, potentially altering admin access paths.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-f4x4-cpmc-ghq4

## What is CVE-2022-3489?

CVE-2022-3489 is a medium-severity missing authorization vulnerability in Unknown Wp-Hide, published on 7 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-3489?

It affects 1 product.


Products: Weberge Wp Hide.

## How do I fix CVE-2022-3489?

No fix has been published for CVE-2022-3489 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-3489 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3489 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3489 and fix it if it is affected.

What it is: CVE-2022-3489 is a medium-severity missing authorization vulnerability in Unknown Wp-Hide, published on 7 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3489 exists.

Affected product: Unknown Wp-Hide. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-3489/ (Markdown: https://insights.sbomify.com/CVE-2022-3489/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3489
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3489
- OSV: https://osv.dev/vulnerability/CVE-2022-3489

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-3489/
Summaries are generated and may contain mistakes; the official description above is the record.