The Events Calendar <= 6.3.0 - Cross-Site Request Forgery to Notice Dismissal
Strategic Overview
- Status
- Patched in 6.3.1
- Affected Plugin
- The Events Calendar
- Affected Version
<= 6.3.0- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-31433
At a glance
CVE-2024-31433 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the The Events Calendar WordPress plugin, affecting versions <= 6.3.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.3.1; sites on affected versions should update now. Disclosed April 2024, reported by Dhabaleshwar Das.
Vulnerability Overview
The The Events Calendar plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 6.3.0. This is due to missing or incorrect nonce validation on the maybe_dismiss() function. This makes it possible for unauthenticated attackers to dismiss notices via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
The Events Calendar <= 6.3.0 carries this weakness at maybe_dismiss(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For The Events Calendar the fix is 6.3.1: builds <= 6.3.0 are affected, anything from 6.3.1 onward is not.
Remediation
Update to version 6.3.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to The Events Calendar: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: The Events Calendar 6.3.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in The Events Calendar
- 9.8CVE-2026-78159: The Events Calendar <= 6.17.3 Code Injection to RCE
CVE-2026-78159 - 9.8CVE-2026-78006: The Events Calendar PHP Object Injection to RCE
CVE-2026-78006 - 9.8CVE-2024-8275: The Events Calendar <= 6.6.4 SQL Injection
CVE-2024-8275 - 8.1CVE-2026-78265: The Events Calendar <= 6.17.2 PHP Object Injection
CVE-2026-78265 - 7.5CVE-2026-49772: The Events Calendar 6.15.12-6.16.2 SQL Injection
CVE-2026-49772 - 7.5CVE-2026-3585: The Events Calendar <= 6.15.17 Arbitrary File Read
CVE-2026-3585 - 7.5CVE-2025-12197: The Events Calendar 6.15.1.1 - 6.15.9 SQL Injection
CVE-2025-12197 - 7.5CVE-2025-9807: The Events Calendar <= 6.15.1 SQL Injection
CVE-2025-9807
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C