☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
Stellarwp logo [ WEBSITE ] [ VENDOR STATS ]
CVSS: 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N 🐛 CWE-352
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2024-31433

CVE-2024-31433 Cross-Site Request Forgery in Stellarwp
📅 PUBLISHED: 2024-04-15 10:15 UTC 🔄 UPDATED: 2026-08-12 14:53 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: Public
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.22%
👁️
0.22% probability
5.5× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1204
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
Country: Estonia License: Freemium
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS VECTOR BREAKDOWN 4.3
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: N Privileges Required None
UI: R User Interaction Required
S: U Scope Unchanged
C: N Confidentiality None
I: L Integrity Low
A: N Availability None
4.3
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2024-31433 is a Cross-Site Request Forgery (CSRF) vulnerability affecting the WordPress plugin The Events Calendar by StellarWP, up to and including version 6.3.0. This vulnerability allows an attacker to trick an authenticated administrator into performing unintended actions, such as modifying event settings or deleting events, without their consent. The attack requires user interaction (clicking a crafted link) and does not directly expose sensitive data, but it can lead to unauthorized configuration changes within the WordPress ecosystem. The EPSS score is 0.0%, indicating low exploitation likelihood in the wild, but the lack of a confirmed patch makes it a persistent risk for unmaintained sites.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

This vulnerability resides in a WordPress plugin distributed via the official WordPress plugin repository. The supply chain risk is moderate: if the plugin is not updated by the vendor, site administrators must manually apply mitigations or remove the plugin. No known malicious packages have been observed exploiting this CVE.

CVSS Breakdown & Threat Level

  • CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
  • Base Score: 4.3 (Medium)
  • Attack Vector: Network (AV:N) – The attacker can trigger the CSRF remotely.
  • Attack Complexity: Low (AC:L) – No special conditions required.
  • Privileges Required: None (PR:N) – The attacker does not need authentication.
  • User Interaction: Required (UI:R) – The victim must click a malicious link or visit a crafted page.
  • Scope: Unchanged (S:U) – The vulnerability does not affect other components.
  • Confidentiality Impact: None (C:N) – No data exposure.
  • Integrity Impact: Low (I:L) – Unauthorized modifications possible.
  • Availability Impact: None (A:N) – No denial of service.

Threat Level: Medium. The CSRF vector requires social engineering, but if exploited, an attacker can alter event data, potentially causing reputational damage or disrupting scheduled events.

Deep Dive & Mechanics

The vulnerability stems from the absence of CSRF nonce validation in certain administrative actions within The Events Calendar plugin. In WordPress, CSRF protection is typically implemented using nonces (number used once) embedded in forms and URLs. The plugin fails to verify these nonces for specific AJAX or POST requests, allowing an attacker to forge requests on behalf of an authenticated administrator.

Attack Flow:

  1. The attacker crafts a malicious HTML page or email containing a hidden form or image tag that submits a request to the victim’s WordPress site (e.g., wp-admin/admin-ajax.php?action=delete_event&event_id=123).
  2. The victim, who is logged in as an administrator, visits the attacker’s page.
  3. The victim’s browser automatically sends the forged request, including their session cookies.
  4. The WordPress server processes the request without checking for a valid nonce, executing the attacker’s action (e.g., deleting an event).

The vulnerability affects all actions that do not implement check_admin_referer() or check_ajax_referer() calls.

Vulnerable vs. Patched Code

Vulnerable Code (<= 6.3.0):

// In a vulnerable AJAX handler
add_action('wp_ajax_delete_event', 'delete_event_callback');
function delete_event_callback() {
    // No nonce check
    $event_id = intval($_POST['event_id']);
    wp_delete_post($event_id, true);
    wp_die();
}

Patched Code (Hypothetical):

// In a patched AJAX handler
add_action('wp_ajax_delete_event', 'delete_event_callback');
function delete_event_callback() {
    // Nonce verification added
    if (!check_ajax_referer('delete_event_nonce', 'nonce', false)) {
        wp_die('CSRF validation failed.');
    }
    $event_id = intval($_POST['event_id']);
    wp_delete_post($event_id, true);
    wp_die();
}

The patch adds a call to check_ajax_referer() with a unique nonce value, ensuring the request originated from the legitimate admin interface.

Exploitation & Lab Setup

Red Team (Attack Simulation)

Prerequisites:

  • A WordPress site with The Events Calendar <= 6.3.0 installed and an admin user logged in.
  • The attacker must host a malicious HTML page.

Exploit Payload (CSRF via Image Tag):

<html>
<body>
<h1>Click me!</h1>
<img src="http://target-site.com/wp-admin/admin-ajax.php?action=delete_event&event_id=1" style="display:none;">
</body>
</html>

Step-by-Step:

  1. Host the above HTML on an attacker-controlled server.
  2. Send the link to the victim (e.g., via phishing email).
  3. When the victim visits the page, the browser sends a GET request to delete event ID 1.
  4. The event is deleted without the victim’s knowledge.

Note: This is a simplified example. Real-world exploitation may require POST requests or additional parameters.

Blue Team (Detection & Defense)

Detection:

  • Monitor for unexpected admin-ajax.php requests with actions like delete_event, update_event, or save_settings without a corresponding nonce parameter.
  • Look for referrer headers that do not match the WordPress admin domain.

Defense:

  • Apply the vendor patch immediately if available.
  • Implement a Web Application Firewall (WAF) rule to block requests to admin-ajax.php that lack a valid nonce.
  • Educate administrators about phishing risks and the importance of logging out after sessions.

Indicators of Compromise (IOCs)

  • Network IOCs:
    • Suspicious requests to /wp-admin/admin-ajax.php with actions related to The Events Calendar (e.g., delete_event, update_event).
    • Referrer headers pointing to external domains.
  • File IOCs:
    • Modified or deleted event posts in the WordPress database.
    • Unexpected entries in the wp_posts table with post type tribe_events.
  • Log IOCs:
    • Repeated admin-ajax.php calls from the same IP without a nonce parameter.
    • User agent strings indicating automated tools.

Detection Engineering

YARA Rule

rule CVE_2024_31433_CSRF_Events_Calendar {
    meta:
        description = "Detects CSRF exploitation attempts against The Events Calendar plugin"
        author = "Valters IT"
        date = "2024-01-01"
        reference = "CVE-2024-31433"
    strings:
        $ajax_action = "admin-ajax.php"
        $event_action = "action=delete_event" nocase
        $event_action2 = "action=update_event" nocase
        $event_action3 = "action=save_settings" nocase
    condition:
        $ajax_action and any of ($event_action*)
}

Sigma Rule

title: CVE-2024-31433 CSRF Exploitation Attempt
id: 7a8b9c0d-1e2f-3a4b-5c6d-7e8f9a0b1c2d
status: experimental
description: Detects HTTP requests targeting The Events Calendar admin-ajax.php without a valid nonce
author: Valters IT
date: 2024-01-01
logsource:
    category: webserver
    product: apache
detection:
    selection:
        cs-method: 'GET'
        c-uri|contains: '/wp-admin/admin-ajax.php'
        cs-uri-query|contains: 
            - 'action=delete_event'
            - 'action=update_event'
            - 'action=save_settings'
    condition: selection
falsepositives:
    - Legitimate admin actions with valid nonces (not easily distinguishable without deep packet inspection)
level: medium

Suricata Rule

alert http any any -> $HOME_NET any (msg:"CVE-2024-31433 CSRF Attempt - The Events Calendar"; flow:to_server,established; content:"/wp-admin/admin-ajax.php"; http_uri; content:"action=delete_event"; http_uri; nocase; sid:1000001; rev:1;)

Remediation & Mitigation

  1. Immediate Action: Disable The Events Calendar plugin if no patch is available and the site is not actively using it.
  2. Vendor Patch: Monitor the StellarWP plugin repository for an update. Apply version 6.3.1 or later as soon as it is released.
  3. Workaround: Implement a custom nonce check by adding the following code to the theme's functions.php:
    add_action('wp_ajax_delete_event', 'custom_csrf_check', 1);
    function custom_csrf_check() {
        if (!check_ajax_referer('delete_event_nonce', 'nonce', false)) {
            wp_die('CSRF validation failed.');
        }
    }
    
  4. WAF Rule: Block requests to admin-ajax.php that do not include a valid nonce parameter.
  5. User Training: Educate administrators on recognizing phishing attempts and the importance of using browser extensions that block CSRF attacks.

Valters IT
Securing Digital Frontiers

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

http.title:"The Events Calendar"
http.html:"wp-content/plugins/the-events-calendar"

💣 PoC CODE AVAILABLE

Exploit code for this CVE is tracked in our database. Access poc_code via API Pro.

[ API_PRO ] →
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2024-31433/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.