CVE-2024-0235 affects the EventON WordPress plugin before versions 4.5.5 and 2.2.7. The vulnerability is caused by missing authorization checks in an AJAX action exposed by the plugin. As a result, an unauthenticated attacker can invoke the affected AJAX functionality and retrieve the email addresses of arbitrary users registered on the WordPress site. Based on the provided information, the issue is an authorization flaw in server-side handling of an AJAX endpoint rather than a memory corruption or code execution bug.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a Python proof-of-concept exploit for CVE-2024-0235, targeting the EventON WordPress plugin (Free <2.2.8, Premium <4.5.5). The exploit script (CVE-2024-0235.py) first checks the version of the EventON plugin by reading the readme.txt file from the plugin directory. If the version is vulnerable, it sends a POST request to the /wp-admin/admin-ajax.php endpoint with the action 'eventon_get_virtual_users', attempting to retrieve email addresses of users by exploiting a missing authorization check. The script extracts and prints any email addresses found in the response. The repository also includes a README.md with usage instructions. The exploit is unauthenticated and leverages a network-based attack vector against WordPress sites running the vulnerable plugin.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.