CVE-2025-58861

7.1 HIGH

📋 TL;DR

A Cross-Site Request Forgery (CSRF) vulnerability in the WordPress Quick Event Calendar plugin allows attackers to trick authenticated administrators into performing unintended actions, which can lead to stored cross-site scripting (XSS) attacks. This affects all WordPress sites running Quick Event Calendar versions up to and including 1.4.9. Attackers can inject malicious scripts that execute when other users visit affected pages.

💻 Affected Systems

Products:
  • WordPress Quick Event Calendar plugin
Versions: n/a through 1.4.9
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with the Quick Event Calendar plugin enabled. Attackers need to trick authenticated users (particularly administrators) into clicking malicious links.

⚠️ 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

An attacker could inject persistent malicious JavaScript that steals administrator credentials, hijacks user sessions, defaces websites, or installs backdoors when users visit calendar pages.

🟠

Likely Case

Attackers create fake calendar events containing malicious scripts that execute when administrators or users view the calendar, potentially leading to session hijacking or credential theft.

🟢

If Mitigated

With proper CSRF protections and input validation, the attack surface is significantly reduced, though the vulnerable code remains present.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires social engineering to trick authenticated users. CSRF attacks are well-understood and weaponization is likely given the stored XSS outcome.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.5.0 or later

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/quick-event-calendar/vulnerability/wordpress-quick-event-calendar-plugin-1-4-9-cross-site-request-forgery-csrf-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find Quick Event Calendar and click 'Update Now' if available. 4. If manual update is needed, download version 1.5.0+ from WordPress.org, deactivate old version, upload new version, and activate.

🔧 Temporary Workarounds

Disable Quick Event Calendar plugin

all

Temporarily deactivate the vulnerable plugin until patching is possible

wp plugin deactivate quick-event-calendar

Implement CSRF protection middleware

all

Add WordPress nonce verification to all plugin form submissions

🧯 If You Can't Patch

  • Restrict plugin access to trusted administrators only using role-based access controls
  • Implement web application firewall (WAF) rules to block suspicious calendar-related POST requests

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Plugins > Installed Plugins for Quick Event Calendar version. If version is 1.4.9 or earlier, you are vulnerable.

Check Version:

wp plugin get quick-event-calendar --field=version

Verify Fix Applied:

After updating, verify the plugin version shows 1.5.0 or later in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to /wp-admin/admin-ajax.php with calendar-related actions
  • Multiple failed nonce verification attempts in WordPress debug logs

Network Indicators:

  • Suspicious calendar event submissions from unexpected referrers
  • POST requests to calendar endpoints without proper CSRF tokens

SIEM Query:

source="wordpress.log" AND ("quick-event-calendar" OR "admin-ajax.php") AND (POST AND calendar)

🔗 References

📤 Share & Export