{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-22215 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-22215 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-22215 is a medium-severity vulnerability in gVectors wpDiscuz, published on 13 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-22215 and fix it if it is affected.\n\nWhat it is: CVE-2026-22215 is a medium-severity vulnerability in gVectors wpDiscuz, published on 13 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-22215 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-22215/ (Markdown: https://insights.sbomify.com/CVE-2026-22215/index.md)","id":"CVE-2026-22215","markdown":"https://insights.sbomify.com/CVE-2026-22215/index.md","name":"CVE-2026-22215","record":{"aliases":["GHSA-p9gr-qppx-mjcg"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can exploit missing CSRF protection to enumerate follow relationships and manipulate user follow data in wpDiscuz.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"wpdiscuz","vendor":"gvectors"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"wpDiscuz before 7.6.47 contains a cross-site request forgery vulnerability in the getFollowsPage() function that allows attackers to trigger unauthorized actions without nonce validation. Attackers can craft malicious requests to enumerate follow relationships and manipulate user follow data by exploiting the missing CSRF protection in the follows page handler.","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 - Missing CSRF Protection on wpdGetFollowsPage","id":"CVE-2026-22215","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"wpDiscuz before 7.6.47 - No Rate Limiting on Subscription Endpoints with LIKE Wildcard Bypass","id":"CVE-2026-22216"},"packages":[],"prev":{"headline":"RIOT OS \u003c= 2026.01-devel-317 Stack-Based Buffer Overflow in ethos Serial Frame Parser","id":"CVE-2026-22214"},"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-13","vendors":["gVectors"]},"summary":"Attackers can exploit missing CSRF protection to enumerate follow relationships and manipulate user follow data in wpDiscuz.","url":"https://insights.sbomify.com/CVE-2026-22215/"}