← WordPress Vulnerabilities
WordPress security by component

VikBooking Hotel Booking Engine & PMS

VikBooking Hotel Booking Engine & PMS is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published May 15, 2025; the highest CVE/CNA score is 8.8.

Plugin slug: vikbooking-hotel-booking-engine-pms

CVE-2024-13616: VikBooking Hotel Booking Engine & PMS: Cross-site scripting

VikBooking Hotel Booking Engine & PMS is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

PublishedMay 15, 2025
Safe version guidanceSee mitigation notes
Safe version
May 15, 2025 CVE-2024-13616
VikBooking Hotel Booking Engine & PMS: Cross-site scripting
VikBooking Hotel Booking Engine & PMS is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE4.8
NVDPending
Jan 26, 2025 CVE-2024-11641
VikBooking Hotel Booking Engine & PMS: Code execution
VikBooking Hotel Booking Engine & PMS is affected by code execution. The vulnerable path is reachable without authentication. Successful exploitation can run attacker-controlled code in the WordPress hosting account.
See mitigation notes
CVE8.8
NVDPending
May 14, 2024 CVE-2024-2749
VikBooking Hotel Booking Engine & PMS: A security weakness
VikBooking Hotel Booking Engine & PMS is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE5.9
NVDPending
May 14, 2024 CVE-2024-2441
VikBooking Hotel Booking Engine & PMS: A security weakness
VikBooking Hotel Booking Engine & PMS is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE8.1
NVDPending