# CVE-2022-4681: Hide My WP < 6.2.9 - Unauthenticated SQLi

> Unauthenticated attackers can exploit SQL injection in the Hide My WP plugin to read or modify database contents.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2023
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-6vgw-7v97-h3ch

## What is CVE-2022-4681?

CVE-2022-4681 is a critical SQL injection vulnerability in Unknown Hide My WP, published on 6 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Hide My WP WordPress plugin before 6.2.9 does not properly sanitize and escape a parameter before using it in a SQL statement via an AJAX action available to unauthenticated users, leading to a SQL injection.

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

It affects 1 product.


Products: Wpwave Hide My Wp.

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

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

## Is CVE-2022-4681 being exploited?

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

Public exploit code:

- Hide My WP < 6.2.9 - Unauthenticated SQLi (exploitdb)

## Other vulnerabilities in Unknown Hide My WP

- [CVE-2021-36916](https://insights.sbomify.com/CVE-2021-36916/): WordPress Hide My WP premium plugin <= 6.2.3 - Unauthenticated SQL injection (SQLi) vulnerability (high 8.6)
- [CVE-2021-36917](https://insights.sbomify.com/CVE-2021-36917/): WordPress Hide My WP premium plugin <= 6.2.3 - Unauthenticated Plugin Deactivation vulnerability (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4681 is a critical SQL injection vulnerability in Unknown Hide My WP, published on 6 Feb 2023. 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-4681 exists.

Affected product: Unknown Hide My WP. 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-4681/ (Markdown: https://insights.sbomify.com/CVE-2022-4681/index.md)
```

## Sources

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

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