Show filters
7 Total Results
Displaying 1-7 of 7
Sort by:
Attacker Value
Unknown
CVE-2025-22719
Disclosure Date: January 21, 2025 (last updated January 22, 2025)
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in E4J s.r.l. VikAppointments Services Booking Calendar allows Stored XSS. This issue affects VikAppointments Services Booking Calendar: from n/a through 1.2.16.
0
Attacker Value
Unknown
CVE-2024-39653
Disclosure Date: August 29, 2024 (last updated September 14, 2024)
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in E4J s.R.L. VikRentCar allows SQL Injection.This issue affects VikRentCar: from n/a through 1.4.0.
0
Attacker Value
Unknown
CVE-2024-1845
Disclosure Date: July 11, 2024 (last updated July 13, 2024)
The VikRentCar Car Rental Management System WordPress plugin before 1.3.2 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions via CSRF attacks
0
Attacker Value
Unknown
CVE-2024-32780
Disclosure Date: April 24, 2024 (last updated April 24, 2024)
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in E4J s.R.L. VikRentCar.This issue affects VikRentCar: from n/a through 1.3.2.
0
Attacker Value
Unknown
CVE-2023-31582
Disclosure Date: October 25, 2023 (last updated November 01, 2023)
jose4j before v0.9.3 allows attackers to set a low iteration count of 1000 or less.
0
Attacker Value
Unknown
CVE-2023-23998
Disclosure Date: April 06, 2023 (last updated November 08, 2023)
Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in E4J s.R.L. VikRentCar Car Rental Management System plugin <= 1.3.0 versions.
0
Attacker Value
Unknown
CVE-2021-24388
Disclosure Date: July 06, 2021 (last updated February 22, 2025)
In the VikRentCar Car Rental Management System WordPress plugin before 1.1.7, there is a custom filed option by which we can manage all the fields that the users will have to fill in before saving the order. However, the field name is not sanitised or escaped before being output back in the page, leading to a stored Cross-Site Scripting issue. There is also no CSRF check done before saving the setting, allowing attackers to make a logged in admin set arbitrary Custom Fields, including one with XSS payload in it.
0