Eventin <= 4.1.17 - Missing Authorization to Authenticated (Subscriber+) Notification Flow Management via notification-flow REST API Endpoint
Strategic Overview
- Status
- Patched in 4.1.18
- Affected Version
<= 4.1.17- CVSS
- 5.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-11821
At a glance
CVE-2026-11821 is a medium-severity Missing Authorization vulnerability in the Eventin WordPress plugin, affecting versions <= 4.1.17. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.1.18; sites on affected versions should update now. Disclosed September 2026, reported by Sushi Com Abacate.
Vulnerability Overview
The Eventin – Event Calendar, Event Registration, Tickets & Booking (AI Powered) plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.1.17. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to view, create, update, clone, and delete notification flow event automation workflows that should be restricted to administrators.
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 interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in Eventin <= 4.1.17 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Eventin the fix is 4.1.18: builds <= 4.1.17 are affected, anything from 4.1.18 onward is not.
Remediation
Update to version 4.1.18, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Eventin 4.1.18 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Eventin – Event Calendar, Tickets, Registration, Booking & WooCommerce
- 8.8CVE-2025-4796: Eventin <= 4.0.34 Privilege Escalation
CVE-2025-4796 - 8.8CVE-2025-39584: Eventin <= 4.0.25 Local File Inclusion
CVE-2025-39584 - 8.8CVE-2025-1770: Event Manager LFI
CVE-2025-1770 - 8.8CVE-2025-26964: Eventin <= 4.0.20 Local File Inclusion
CVE-2025-26964 - 8.8CVE-2024-56213: Eventin <= 4.0.7 Local File Inclusion
CVE-2024-56213 - 8.8CVE-2024-7149: Event Manager LFI
CVE-2024-7149 - 7.5CVE-2026-15667: Eventin <= 4.1.22 Local File Inclusion
CVE-2026-15667 - 7.5CVE-2026-15406: Eventin <= 4.1.22 Local File Inclusion
CVE-2026-15406
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C