Filtered by vendor Zephyr-one Subscriptions
Filtered by product Zephyr Project Manager Subscriptions
Total 5 CVE
CVE Vendors Products Updated CVSS v3.1
CVE-2022-2840 1 Zephyr-one 1 Zephyr Project Manager 2024-09-03 9.8 Critical
The Zephyr Project Manager WordPress plugin before 3.2.5 does not sanitise and escape various parameters before using them in SQL statements via various AJAX actions available to both unauthenticated and authenticated users, leading to SQL injections
CVE-2024-43915 1 Zephyr-one 1 Zephyr Project Manager 2024-08-28 5.5 Medium
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Dylan James Zephyr Project Manager allows Reflected XSS.This issue affects Zephyr Project Manager: from n/a through .3.102.
CVE-2024-7624 1 Zephyr-one 1 Zephyr Project Manager 2024-08-15 8.1 High
The Zephyr Project Manager plugin for WordPress is vulnerable to limited privilege escalation in all versions up to, and including, 3.3.101. This is due to the plugin not properly checking a users capabilities before allowing them to enable access to the plugin's settings through the update_user_access() function. This makes it possible for authenticated attackers, with subscriber-level access and above, to grant themselves full access to the plugin's settings.
CVE-2022-3333 1 Zephyr-one 1 Zephyr Project Manager 2024-08-03 3.5 Low
A vulnerability, which was classified as problematic, was found in Zephyr Project Manager up to 3.2.4. Affected is an unknown function of the file /v1/tasks/create/ of the component REST Call Handler. The manipulation of the argument onanimationstart leads to cross site scripting. It is possible to launch the attack remotely. Upgrading to version 3.2.5 is able to address this issue. It is recommended to upgrade the affected component. VDB-209370 is the identifier assigned to this vulnerability.
CVE-2022-2839 1 Zephyr-one 1 Zephyr Project Manager 2024-08-03 5.4 Medium
The Zephyr Project Manager WordPress plugin before 3.2.55 does not have any authorisation as well as CSRF in all its AJAX actions, allowing unauthenticated users to call them either directly or via CSRF attacks. Furthermore, due to the lack of sanitisation and escaping, it could also allow them to perform Stored Cross-Site Scripting attacks against logged in admins.