Loading vulnerability…
Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered) for WordPress through version 4.1.22 is vulnerable to authenticated local file inclusion through insufficient validation of the event_layout parameter. An authenticated user with Contributor-level privileges or higher can set a malicious layout value through the plugin REST API, causing server-side inclusion and execution of arbitrary PHP files already accessible to the web server. Contributors receive the etn_manage_event capability by default, enabling exploitation without additional capability configuration.
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 three-file repository is a standalone Python 3 proof-of-concept/exploitation utility for CVE-2026-15667 in the Eventin WordPress plugin (wp-event-solution) through version 4.1.22. Its sole code file, cve-2026-15667-eventin-lfi.py, uses only the Python standard library and implements HTTP session handling, cookies, WordPress authentication or supplied session-cookie use, redirect preservation for login POSTs, compression decoding, TLS handling, and HTTP/HTTPS fallback. It fingerprints the public Eventin readme and REST events route in guest test mode, while authenticated mode obtains the required REST nonce and uses the event_layout REST field to store a traversal-based layout value. The vulnerable plugin subsequently includes the chosen layout with a .php suffix, enabling local file disclosure where the effective appended path exists. README.md documents invocation, privilege requirements, output states, and examples; LICENSE is MIT. No reverse shell, command execution payload, persistence mechanism, or third-party exploit framework is present.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.