Vulnerabilities > Gvectors > Wpdiscuz
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 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-08-24 | CVE-2020-24186 | Unrestricted Upload of File with Dangerous Type vulnerability in Gvectors Wpdiscuz A Remote Code Execution vulnerability exists in the gVectors wpDiscuz plugin 7.0 through 7.0.4 for WordPress, which allows unauthenticated users to upload any type of file, including PHP files via the wmuUploadFiles AJAX action. | 10.0 |
| 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 |