Vulnerabilities > Gvectors > Wpdiscuz > 2.1.9
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2023-10-20 | CVE-2023-3998 | Missing Authorization vulnerability in Gvectors Wpdiscuz The wpDiscuz plugin for WordPress is vulnerable to unauthorized modification of data due to a missing authorization check on the userRate function in versions up to, and including, 7.6.3. | 5.3 |
| 2022-02-21 | CVE-2022-23984 | Information Exposure vulnerability in Gvectors Wpdiscuz Sensitive information disclosure discovered in wpDiscuz WordPress plugin (versions <= 7.3.11). | 7.5 |
| 2021-11-08 | CVE-2021-24806 | Cross-Site Request Forgery (CSRF) vulnerability in Gvectors Wpdiscuz The wpDiscuz WordPress plugin before 7.3.4 does check for CSRF when adding, editing and deleting comments, which could allow attacker to make logged in users such as admin edit and delete arbitrary comment, or the user who made the comment to edit it via a CSRF attack. | 4.3 |
| 2021-10-11 | CVE-2021-24737 | Unspecified vulnerability in Gvectors Wpdiscuz The Comments – wpDiscuz WordPress plugin through 7.3.0 does not properly sanitise or escape the Follow and Unfollow messages before outputting them in the page, which could allow high privilege users to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed. | 4.8 |
| 2020-06-18 | CVE-2020-13640 | SQL Injection vulnerability in Gvectors Wpdiscuz A SQL injection issue in the gVectors wpDiscuz plugin 5.3.5 and earlier for WordPress allows remote attackers to execute arbitrary SQL commands via the order parameter of a wpdLoadMoreComments request. | 9.8 |