{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-22216 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-22216 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-22216 is a medium-severity denial of service vulnerability in gVectors wpDiscuz, published on 13 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-22216 and fix it if it is affected.\n\nWhat it is: CVE-2026-22216 is a medium-severity denial of service vulnerability in gVectors wpDiscuz, published on 13 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-22216 in the wild and no public exploit code.\n\nAffected product: gVectors wpDiscuz. 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-2026-22216/ (Markdown: https://insights.sbomify.com/CVE-2026-22216/index.md)","id":"CVE-2026-22216","markdown":"https://insights.sbomify.com/CVE-2026-22216/index.md","name":"CVE-2026-22216","record":{"aliases":["GHSA-9j2r-2287-24hf"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can spam arbitrary email addresses with post notifications by exploiting missing rate limits and wildcard bypasses in wpDiscuz.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"wpdiscuz","vendor":"gvectors"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-799","name":"Improper Control of Interaction Frequency"}],"description":"wpDiscuz before 7.6.47 contains a missing rate limiting vulnerability that allows unauthenticated attackers to subscribe arbitrary email addresses to post notifications by sending POST requests to the wpdAddSubscription handler in class.WpdiscuzHelperAjax.php. Attackers can exploit LIKE wildcard characters in the subscription query to match multiple email addresses and generate unwanted notification emails to victim accounts.","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":"wpDiscuz before 7.6.47 - No Rate Limiting on Subscription Endpoints with LIKE Wildcard Bypass","id":"CVE-2026-22216","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"OpenClaw 2026.2.22 \u003c 2026.2.23 - Arbitrary Binary Execution via $SHELL Environment Variable Trusted Prefix Fallback","id":"CVE-2026-22217"},"packages":[],"prev":{"headline":"wpDiscuz before 7.6.47 - Missing CSRF Protection on wpdGetFollowsPage","id":"CVE-2026-22215"},"products":["wpDiscuz"],"published":"2026-03-13","related":[{"cvss_score":10,"headline":"File upload in n/a","id":"CVE-2020-24186","kev_date_added":null,"published":"2020-08-24"},{"cvss_score":9.8,"headline":"Comments – wpDiscuz \u003c= 7.6.24 - Authentication Bypass via WordPress.com OAuth provider","id":"CVE-2024-9488","kev_date_added":null,"published":"2024-10-25"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-13640","kev_date_added":null,"published":"2020-06-18"},{"cvss_score":9.2,"headline":"wpDiscuz before 7.6.47 - SQL Injection in getAllSubscriptions()","id":"CVE-2026-22193","kev_date_added":null,"published":"2026-03-13"},{"cvss_score":8.8,"headline":"Voltronic Power SNMP Web Pro 1.1 Authentication Bypass via localStorage","id":"CVE-2026-22192","kev_date_added":null,"published":"2026-03-13"},{"cvss_score":8.7,"headline":"wpDiscuz before 7.6.47 - Unauthenticated Email Notification Flood via wpdCheckNotificationType","id":"CVE-2026-22182","kev_date_added":null,"published":"2026-03-13"},{"cvss_score":8.7,"headline":"Voltronic Power SNMP Web Pro 1.1 Path Traversal via upload.cgi","id":"CVE-2026-22199","kev_date_added":null,"published":"2026-03-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-03-13","vendors":["gVectors"]},"summary":"Unauthenticated attackers can spam arbitrary email addresses with post notifications by exploiting missing rate limits and wildcard bypasses in wpDiscuz.","url":"https://insights.sbomify.com/CVE-2026-22216/"}