The EventCalendar WordPress plugin before 1.1.51 does not escape some user input before outputting it back in attributes, leading to Reflected Cross-SIte Scripting issues
Product
wordpress event-calendar-wd vulnerabilities
6 published CVES affecting wordpress event-calendar-wd, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 0
- High
- 1
- Medium
- 5
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress event-calendar-wd CVEs
Newest publication first
-
MediumCVSS 6.1 EPSS 0.84%
-
MediumCVSS 4.3 EPSS 0.36%
The EventCalendar WordPress plugin before 1.1.51 does not have proper authorisation and CSRF checks in the add_calendar_event AJAX actions, allowing users with a role as low as subscriber to create events
-
WORDFENCE-1d430b33-1607-46b3-8780-ac5cfbb7d6ec EventCalendar <= 1.1.45 - Cross-Site Scripting
PublishedMediumCVSS 4.7The Event Calendar WD plugin for WordPress is vulnerable to Cross-Site Scripting in versions up to, and including, 1.1.45 due to insufficient input sanitization and output escaping. This makes it possible for attackers to inject arbitrary web scripts that execute in a victim's br...
-
WORDFENCE-0d5a0c05-736f-4fb9-9358-894977664bf4 Event Calendar <= 1.1.44 - Cross-Site Scripting
PublishedHighCVSS 7.2The Event Calendar WD plugin for WordPress is vulnerable to Cross-Site Scripting in versions up to, and including, 1.1.44 due to insufficient input sanitization and output escaping. This makes it possible for attackers to inject arbitrary web scripts in pages that will execute wh...
-
MediumCVSS 5.4 EPSS 1.2%
Cross-site scripting vulnerability in Event Calendar WD version 1.1.21 and earlier allows remote authenticated attackers to inject arbitrary web script or HTML via unspecified vectors.
-
MediumCVSS 6.1 EPSS 1.5%
Cross-site scripting vulnerability in Event Calendar WD prior to version 1.0.94 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
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.