The Events Made Easy plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.2.5 via the eme_single_event_page_template function. This makes it possible for authenticated attackers, with contributor-level access and above, to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. The stored traversal payload is triggered passively when any visitor loads the affected single-event page, meaning post-submission execution does not require additional attacker interaction.
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
The Events Made Easy WordPress plugin contains a critical Local File Inclusion (LFI) vulnerability in the eme_single_event_page_template function that allows authenticated attackers with contributor-level privileges to include and execute arbitrary PHP files on the server. This vulnerability (CVE-2026-75963, CVSS 7.5) is particularly dangerous because it bridges the gap between low-privilege account access and full code execution. WordPress sites using this plugin up to version 3.2.5 are at risk, especially those with open contributor registration or compromised contributor accounts. The ability to execute arbitrary PHP code enables attackers to bypass access controls, exfiltrate sensitive data, establish persistence, or pivot to compromise the underlying server infrastructure.
While Casky currently shows zero matching skills for this specific CVE, a comprehensive defense strategy would leverage Claude AI's extended reasoning to detect the attack patterns underlying LFI exploitation. Practitioners should monitor for suspicious file path parameters in requests to the eme_single_event_page_template function, looking for directory traversal sequences (../, ..\, or encoded variants) and attempts to include sensitive files like wp-config.php or /etc/passwd. Detection logic would flag POST/GET requests from contributor-level accounts containing PHP file references or null byte injection attempts. Organizations using Casky should note that while formal MITRE ATT&CK mappings aren't available for this CVE, the exploitation pattern maps to Defense Evasion techniques (T1548 - Abuse Elevation Control Mechanism) and Execution (T1059 - Command and Scripting Interpreter). Immediate action includes updating to version 3.2.6 or later, auditing contributor account activity, and reviewing file inclusion logs for indicators of compromise.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-75963. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation