VYPR

Latepoint

by WordPress

Source repositories

CVEs (26)

  • CVE-2025-3769MedMay 14, 2025
    risk 0.27cvss 5.3epss 0.00

    The LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.1.92 via the 'view_booking_summary_in_lightbox' due to missing validation on a user controlled…

  • CVE-2026-9719MedJun 6, 2026
    risk 0.21cvss 4.3epss 0.00

    The LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.6.0. This is due to missing or incorrect nonce validation on the change_status function. This makes it…

  • CVE-2026-5365MedMay 14, 2026
    risk 0.21cvss 4.3epss 0.00

    The LatePoint plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 5.3.2. This is due to missing nonce verification on the request_cancellation() function. This makes it possible for unauthenticated attackers to cancel a logged-in…

  • CVE-2025-14873MedFeb 14, 2026
    risk 0.21cvss 4.3epss 0.00

    The LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.2.5. This is due to the 'call_by_route_name' function in the routing layer only validating user…

  • CVE-2024-8943Oct 8, 2024
    risk 0.03cvss epss 0.03

    The LatePoint plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 5.0.12. This is due to insufficient verification on the user being supplied during the booking customer step. This makes it possible for unauthenticated attackers to log…

  • CVE-2024-8911Oct 8, 2024
    risk 0.02cvss epss 0.03

    The LatePoint plugin for WordPress is vulnerable to Arbitrary User Password Change via SQL Injection in versions up to, and including, 5.0.11. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This…

Page 2 of 2