Vulnerabilities (CVE)

Filtered by vendor 2code Subscribe
Total 13 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2022-3688 1 2code 1 Wpqa Builder 2023-12-10 N/A 8.8 HIGH
The WPQA Builder WordPress plugin before 5.9 does not have CSRF check when following and unfollowing users, which could allow attackers to make logged in users perform such actions via CSRF attacks
CVE-2022-3343 1 2code 1 Wpqa Builder 2023-12-10 N/A 3.5 LOW
The WPQA Builder WordPress plugin before 5.9.3 (which is a companion plugin used with Discy and Himer Discy WordPress themes) incorrectly tries to validate that a user already follows another in the wpqa_following_you_ajax action, allowing a user to inflate their score on the site by having another user send repeated follow actions to them.
CVE-2022-1323 1 2code 1 Discy 2023-12-10 N/A 6.5 MEDIUM
The Discy WordPress theme before 5.0 lacks authorization checks then processing ajax requests to the discy_update_options action, allowing any logged in users (with privileges as low as Subscriber,) to change Theme options by sending a crafted POST request.
CVE-2022-2198 1 2code 1 Wpqa Builder 2023-12-10 N/A 4.3 MEDIUM
The WPQA Builder WordPress plugin before 5.7 which is a companion plugin to the Hilmer and Discy , does not check authorization before displaying private messages, allowing any logged in user to read other users private message using the message id, which can easily be brute forced.
CVE-2022-1241 1 2code 1 Ask Me 2023-12-10 4.3 MEDIUM 6.1 MEDIUM
The Ask me WordPress theme before 6.8.2 does not properly sanitise and escape several of the fields in the Edit Profile page, leading to Reflected Cross-Site Scripting issues
CVE-2022-1051 1 2code 1 Wpqa Builder 2023-12-10 3.5 LOW 5.4 MEDIUM
The WPQA Builder Plugin WordPress plugin before 5.2, used as a companion plugin for the Discy and Himer , does not sanitise and escape the city, phone or profile credentials fields when outputting it in the profile page, allowing any authenticated user to perform Cross-Site Scripting attacks.
CVE-2022-1598 1 2code 1 Wpqa Builder 2023-12-10 5.0 MEDIUM 5.3 MEDIUM
The WPQA Builder WordPress plugin before 5.5 which is a companion to the Discy and Himer , lacks authentication in a REST API endpoint, allowing unauthenticated users to discover private questions sent between users on the site.
CVE-2022-1597 1 2code 1 Wpqa Builder 2023-12-10 4.3 MEDIUM 6.1 MEDIUM
The WPQA Builder WordPress plugin before 5.4, used as a companion for the Discy and Himer , does not sanitise and escape a parameter on its reset password form which makes it possible to perform Reflected Cross-Site Scripting attacks
CVE-2022-1425 1 2code 1 Wpqa Builder 2023-12-10 4.0 MEDIUM 4.3 MEDIUM
The WPQA Builder Plugin WordPress plugin before 5.2, used as a companion plugin for the Discy and Himer , does not validate that the message_id of the wpqa_message_view ajax action belongs to the requesting user, leading to any user being able to read messages for any other users via a Insecure Direct Object Reference (IDOR) vulnerability.
CVE-2022-1422 1 2code 1 Discy 2023-12-10 4.3 MEDIUM 6.5 MEDIUM
The Discy WordPress theme before 5.2 does not check for CSRF tokens in the AJAX action discy_reset_options, allowing an attacker to trick an admin into resetting the site settings back to defaults.
CVE-2022-1349 1 2code 1 Wpqa Builder 2023-12-10 4.0 MEDIUM 4.3 MEDIUM
The WPQA Builder Plugin WordPress plugin before 5.2, used as a companion plugin for the Discy and Himer , does not validate that the value passed to the image_id parameter of the ajax action wpqa_remove_image belongs to the requesting user, allowing any users (with privileges as low as Subscriber) to delete the profile pictures of any other user.
CVE-2022-1421 1 2code 1 Discy 2023-12-10 4.3 MEDIUM 4.3 MEDIUM
The Discy WordPress theme before 5.2 lacks CSRF checks in some AJAX actions, allowing an attacker to make a logged in admin change arbitrary 's settings including payment methods via a CSRF attack
CVE-2022-1424 1 2code 1 Ask Me 2023-12-10 4.3 MEDIUM 6.5 MEDIUM
The Ask me WordPress theme before 6.8.2 does not perform CSRF checks for any of its AJAX actions, allowing an attacker to trick logged in users to perform various actions on their behalf on the site.