The VR Calendar plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.4.7. This is due to missing or incorrect nonce validation on the syncCalendar() function. This makes it possible for unauthenticated attackers to trigger a cal...
Product
wordpress vr-calendar-sync vulnerabilities
6 published CVES affecting wordpress vr-calendar-sync, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 1
- High
- 1
- Medium
- 4
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress vr-calendar-sync CVEs
Newest publication first
-
MediumCVSS 4.3 EPSS 0.14%
-
HighCVSS 7.5 EPSS 0.57%
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Innate Images LLC VR Calendar vr-calendar-sync allows PHP Local File Inclusion.This issue affects VR Calendar: from n/a through <= 2.4.0.
-
MediumCVSS 6.5 EPSS 0.62%
The VR Calendar plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.3.3. This is due to missing or incorrect nonce validation on several functions. This makes it possible for unauthenticated attackers to delete, and modify calendar...
-
CriticalCVSS 9.8 EPSS 17.2% Scanner template
The VR Calendar WordPress plugin through 2.3.2 lets any user execute arbitrary PHP functions on the site.
-
MediumCVSS 6.8
The VR Calendar plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 2.4.4. This makes it possible for administrator-level attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files...
-
WORDFENCE-17cb7420-b4e1-4959-beae-d3c0a8c4b1ff VR Calendar <= 2.3.1 - Reflected Cross-Site Scripting
PublishedMediumCVSS 6.1The VR Calendar for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'vrc_msg' and 'vrc_msg_type' parameters in versions up to, and including, 2.3.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers t...
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.