# CVE-2022-51021: NotificationX WordPress Plugin < 2.3.12 Unauthenticated SQL Injection via notification REST endpoint


- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-ch24-62hg-vfpg

## What is CVE-2022-51021?

CVE-2022-51021 is a high-severity vulnerability in WPDeveloper NotificationX, published on 22 Oct 2026. 

### Official description

NotificationX plugin for WordPress 2.0.0 before 2.3.12 contains an unauthenticated SQL injection vulnerability that allows remote attackers to manipulate database queries by supplying an array-form 'id' parameter to /wp-json/notificationx/v1/notification/{id}. Attackers can pass id[1] with crafted SQL, such as time-based SLEEP payloads, along with an api_key derived from md5(home_url()), which flows unsanitized into Database::get_where_query to extract database contents. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-18.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2022-51021 being exploited?

There is no known exploitation of CVE-2022-51021 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-51021 is a high-severity vulnerability in WPDeveloper NotificationX, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2022-51021 in the wild and no public exploit code.

Affected product: WPDeveloper NotificationX. 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-51021/ (Markdown: https://insights.sbomify.com/CVE-2022-51021/index.md)
```

## Sources

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

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