{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-51021 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-51021 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-51021 is a high-severity vulnerability in WPDeveloper NotificationX, published on 22 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2022-51021 and fix it if it is affected.\n\nWhat it is: CVE-2022-51021 is a high-severity vulnerability in WPDeveloper NotificationX, published on 22 Oct 2026. \nExploitation: There is no known exploitation of CVE-2022-51021 in the wild and no public exploit code.\n\nAffected product: WPDeveloper NotificationX. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-51021/ (Markdown: https://insights.sbomify.com/CVE-2022-51021/index.md)","id":"CVE-2022-51021","markdown":"https://insights.sbomify.com/CVE-2022-51021/index.md","name":"CVE-2022-51021","record":{"aliases":["GHSA-ch24-62hg-vfpg"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"NotificationX WordPress Plugin \u003c 2.3.12 Unauthenticated SQL Injection via notification REST endpoint","id":"CVE-2022-51021","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"YiShaAdmin 3.1 Unauthenticated Path Traversal via DownloadFile endpoint","id":"CVE-2022-51022"},"packages":[],"prev":{"headline":"Flower before 2.2.0 CSRF via Worker and Task Control API Endpoints","id":"CVE-2022-51020"},"products":["NotificationX"],"published":"2026-10-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-23","vendors":["WPDeveloper"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2022-51021/"}