Quick answers
- Is CVE-2022-51021 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-51021 being exploited in the wild.
- How severe is CVE-2022-51021?
- High severity, with a CVSS score of 8.2, published 22 October 2026.
- Which products and versions are affected?
- WPDeveloper NotificationX 2.0.0 to 2.3.11.
- Is there a fix for CVE-2022-51021?
- Yes: fixed in 2.3.12. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-51021 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2022-51021?
- Check whether you run WPDeveloper NotificationX at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.3.12
Technical details
The plugin fails to validate and sanitize the array-form 'id' parameter in the /wp-json/notificationx/v1/notification/{id} REST endpoint before passing it to SQL queries. An attacker can supply id[1] with crafted SQL payloads (such as time-based SLEEP injections) along with an api_key derived from md5(home_url()) to execute arbitrary queries in the Database::get_where_query function. This is an unauthenticated, network-accessible vulnerability with no user interaction required.
Affected products
- WPDeveloper NotificationX 2.0.0 to 2.3.11
Timeline
- 2022: disclosed
- 2023-10-18: exploited: Exploitation observed by Shadowserver Foundation
- 2026-10-22: advisory