The Booking for Appointments and Events Calendar – Amelia plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 1.2. This is due to the plugin utilizing Symfony and leaving display_errors on within test files. This makes it possible for...
Product
tms-outsource amelia vulnerabilities
13 published CVES affecting tms-outsource amelia, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 13
- Critical
- 1
- High
- 1
- Medium
- 11
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest tms-outsource amelia CVEs
Newest publication first
-
MediumCVSS 5.3 EPSS 0.44%
-
MediumCVSS 4.8 EPSS 0.26%
The Booking for Appointments and Events Calendar – Amelia plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.1.5 (and 7.5.1 for the Pro version) due to insufficient input sanitization and output escaping. T...
-
CriticalCVSS 9.8 EPSS 0.38%
Missing Authorization vulnerability in TMS Amelia ameliabooking.This issue affects Amelia: from n/a through 1.0.98.
-
MediumCVSS 5.4 EPSS 0.52%
The Booking for Appointments and Events Calendar – Amelia plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's shortcode(s) in all versions up to, and including, 1.0.93 due to insufficient input sanitization and output escaping on user supplied attri...
-
CVE-2023-50860 WordPress Amelia Plugin <= 1.0.85 is vulnerable to Cross Site Scripting (XSS)
PublishedMediumCVSS 5.4 EPSS 0.33%Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in TMS Booking for Appointments and Events Calendar – Amelia allows Stored XSS.This issue affects Booking for Appointments and Events Calendar – Amelia: from n/a through 1.0.85.
-
CVE-2023-29427 WordPress Amelia Plugin <= 1.0.75 is vulnerable to Cross Site Scripting (XSS)
PublishedMediumCVSS 6.1 EPSS 0.41%Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in TMS Booking for Appointments and Events Calendar – Amelia plugin <= 1.0.75 versions.
-
MediumCVSS 6.1 EPSS 0.51%
Cross-site scripting vulnerability in Appointment and Event Booking Calendar for WordPress - Amelia versions prior to 1.0.76 allows a remote unauthenticated attacker to inject an arbitrary script by having a user who is logging in the WordPress where the product is installed visi...
-
MediumCVSS 5.4 EPSS 0.62%
The Amelia WordPress plugin before 1.0.48 does not have proper authorisation when handling Amelia SMS service, allowing any customer to send paid test SMS notification as well as retrieve sensitive information about the admin, such as the email, account balance and payment histor...
-
MediumCVSS 5.4 EPSS 0.80%
The Amelia WordPress plugin before 1.0.49 does not have proper authorisation when managing appointments, allowing any customer to update other's booking status, as well as retrieve sensitive information about the bookings, such as the full name and phone number of the person who...
-
MediumCVSS 5.4 EPSS 0.62%
The Amelia WordPress plugin before 1.0.47 does not have proper authorisation when managing appointments, allowing any customer to update other's booking, as well as retrieve sensitive information about the bookings, such as the full name and phone number of the person who booked...
-
HighCVSS 8.8 EPSS 1.5%
The Amelia WordPress plugin before 1.0.47 stores image blobs into actual files whose extension is controlled by the user, which may lead to PHP backdoors being uploaded onto the site. This vulnerability can be exploited by logged-in users with the custom "Amelia Manager" role.
-
MediumCVSS 6.1 EPSS 0.80%
The Amelia WordPress plugin before 1.0.47 does not sanitize and escape the code parameter before outputting it back in an admin page, leading to a Reflected Cross-Site Scripting.
-
MediumCVSS 4.3 EPSS 0.43%
The Amelia WordPress plugin before 1.0.47 does not have CSRF check in place when deleting customers, which could allow attackers to make a logged in admin delete arbitrary customers via a CSRF attack
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.