WP FullCalendar vulnerabilities
Plugin slug wp-fullcalendar · 4 known vulnerabilities · latest disclosed 2026-02-11 · WordPress.org page
Every listed vulnerability has a fix. Version 1.6.1 or later is not affected by any of them. If your site runs an older version, update it.
0 of 4 rated high or critical (CVSS 7 or more).
Known vulnerabilities in WP FullCalendar
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 5.3 | <= 1.6 | 1.6.1 | CVE-2026-22351 | 2026-02-11 | Advisory |
| Medium 5.3 | <= 1.6 | 1.6.1 | CVE-2026-24523 | 2026-01-26 | Advisory |
| Medium 6.4 | <= 1.5 | 1.6 | CVE-2025-22261 | 2025-01-06 | Advisory |
| Medium 6.5 | <= 1.4.1 | 1.5 | CVE-2022-3891 | 2023-01-17 | Advisory |
Check if a site is affected
Enter a site address to see which version of WP FullCalendar and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the WP FullCalendar plugin safe to use?
All 4 known issues are fixed in current versions (1.6.1 or later). Keeping it updated is what matters.
How do I check which version of WP FullCalendar my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.