CVE-2025-22261

6.5 MEDIUM

📋 TL;DR

This stored cross-site scripting (XSS) vulnerability in the WP FullCalendar WordPress plugin allows attackers to inject malicious scripts into web pages. When users view pages containing the injected scripts, the attacker can steal session cookies, redirect users, or perform actions on their behalf. All WordPress sites using WP FullCalendar versions up to 1.5 are affected.

💻 Affected Systems

Products:
  • WP FullCalendar WordPress Plugin
Versions: All versions up to and including 1.5
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in the calendar functionality where user input is not properly sanitized before being displayed.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal administrator session cookies, take over WordPress sites, install backdoors, deface websites, or redirect visitors to malicious sites.

🟠

Likely Case

Attackers inject malicious JavaScript that steals user session cookies or redirects users to phishing pages when they view calendar pages.

🟢

If Mitigated

With proper input validation and output escaping, malicious scripts would be neutralized before reaching users.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

XSS vulnerabilities are commonly exploited, though specific exploit details for this CVE aren't publicly documented.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Version after 1.5

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/wp-fullcalendar/vulnerability/wordpress-wp-fullcalendar-plugin-1-5-cross-site-scripting-xss-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find WP FullCalendar and check if update is available. 4. Click 'Update Now' if update exists. 5. If no update appears, deactivate and remove the plugin immediately.

🔧 Temporary Workarounds

Disable WP FullCalendar Plugin

all

Temporarily disable the vulnerable plugin until patched version is available

wp plugin deactivate wp-fullcalendar

Implement WAF Rules

all

Add web application firewall rules to block XSS payloads targeting calendar endpoints

🧯 If You Can't Patch

  • Remove WP FullCalendar plugin completely and use alternative calendar solutions
  • Implement Content Security Policy (CSP) headers to restrict script execution sources

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin → Plugins → Installed Plugins for WP FullCalendar version ≤1.5

Check Version:

wp plugin get wp-fullcalendar --field=version

Verify Fix Applied:

Verify WP FullCalendar version is greater than 1.5 in WordPress plugins list

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to calendar endpoints with script tags
  • Multiple failed XSS attempts in web server logs

Network Indicators:

  • HTTP requests containing <script> tags to /wp-content/plugins/wp-fullcalendar/ endpoints

SIEM Query:

source="web_server" AND (uri="*wp-fullcalendar*" AND (body="*<script>*" OR body="*javascript:*"))

🔗 References

📤 Share & Export