VYPR

Timetable and Event Schedule

by WordPress

CVEs (6)

  • CVE-2020-36840Oct 16, 2024
    risk 0.00cvss epss 0.00

    The Timetable and Event Schedule by MotoPress plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the wp_ajax_route_url() function called via a nopriv AJAX action in versions up to, and including, 2.3.8. This makes it possible for…

  • CVE-2022-2844Aug 16, 2022
    risk 0.00cvss epss 0.00

    A vulnerability classified as problematic has been found in MotoPress Timetable and Event Schedule up to 1.4.06. This affects an unknown part of the file /wp/?cpmvc_id=1&cpmvc_do_action=mvparse&f=datafeed&calid=1&month_index=1&method=adddetails&id=2 of the component Calendar…

  • CVE-2022-2843Aug 16, 2022
    risk 0.00cvss epss 0.00

    A vulnerability was found in MotoPress Timetable and Event Schedule. It has been rated as problematic. Affected by this issue is some unknown functionality of the file /wp-admin/admin-ajax.php of the component Quick Edit. The manipulation of the argument post_title with the…

  • CVE-2021-24585Sep 20, 2021
    risk 0.00cvss epss 0.01

    The Timetable and Event Schedule WordPress plugin before 2.4.0 outputs the Hashed Password, Username and Email Address (along other less sensitive data) of the user related to the Even Head of the Timeslot in the response when requesting the event Timeslot data with a user with…

  • CVE-2021-24584Sep 20, 2021
    risk 0.00cvss epss 0.00

    The Timetable and Event Schedule WordPress plugin before 2.4.2 does not have proper access control when updating a timeslot, allowing any user with the edit_posts capability (contributor+) to update arbitrary timeslot from any events. Furthermore, no CSRF check is in place as…

  • CVE-2021-24583Sep 20, 2021
    risk 0.00cvss epss 0.02

    The Timetable and Event Schedule WordPress plugin before 2.4.2 does not have proper access control when deleting a timeslot, allowing any user with the edit_posts capability (contributor+) to delete arbitrary timeslot from any events. Furthermore, no CSRF check is in place as…